3 ms·
Author here. I mainly used node's `--cpu-prof` flag to generate a profile. Tried loading the trace into Chrome DevTools at first, but wasn't able to load the f
by mhagemeister 4y ago
Author here.
I mainly used node's `--cpu-prof` flag to generate a profile. Tried loading the trace into Chrome DevTools at first, but wasn't able to load the file supposedly because they are too big. So I used https://www.speedscope.app/ https://www.speedscope.app/ instead and which loaded them without any issues and is very snappy overall. What's more is that it allows you to display a left-heavy flamegraph which makes it much easier to spot functions taking up a lot of time. Speedscope is an amazing tool!
For webpack based projects the traces were missing quite a bit of data and I had more luck with their own profiling plugin: https://webpack.js.org/plugins/profiling-plugin/ https://webpack.js.org/plugins/profiling-plugin/
- semiquaver 4y agoSpeedscope is the best.
- romellem 4y agoAwesome, thanks! I too have found Chrome's profiler lacking, so will definitely have to check out https://www.speedscope.app/ https://www.speedscope.app/.