You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
4. Disregard warnings unless they're saying you can't run perf due to missing packages; you may get some warnings about not being able to access kernel module samples which you're not after anyway.
42
42
5. Run `perf script > perfs.out` to generate the data file you'll visualize in a moment. It's useful to [apply some cleanup](#filtering-out-nodejs-internal-functions) for a more readable graph
43
43
6. Preview or generate the flame graph:
44
-
45
-
- Browser preview (no local setup required):
46
-
47
-
- Upload the generated `perfs.out` file to <https://flamegraph.com> to visualize the flame graph.
- Run `cat perfs.out | ./FlameGraph/stackcollapse-perf.pl | ./FlameGraph/flamegraph.pl --colors=js > profile.svg` and now open the flame graph file in your favorite browser and watch it burn
44
+
- Browser preview (no local setup required):
45
+
- Upload the generated `perfs.out` file to <https://flamegraph.com> to visualize the flame graph.
- Run `cat perfs.out | ./FlameGraph/stackcollapse-perf.pl | ./FlameGraph/flamegraph.pl --colors=js > profile.svg` and now open the flame graph file in your favorite browser and watch it burn
52
49
53
50
Once the flame graph is rendered, inspect the most saturated orange bars first. They're likely to represent CPU heavy functions.
0 commit comments