Currently the profiler always shows the garbage collector as being the hotspot and doesn't give any information on actual user code. Using the V8 profiler with node --prof-cpu and loading the file into Chrome Dev-Tools suggests this is probably due to the top down interpretation of the profiler data, while a bottom up visualization yields more relevant results.
Currently the profiler always shows the garbage collector as being the hotspot and doesn't give any information on actual user code. Using the V8 profiler with
node --prof-cpuand loading the file into Chrome Dev-Tools suggests this is probably due to the top down interpretation of the profiler data, while a bottom up visualization yields more relevant results.