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
Copy file name to clipboardExpand all lines: apps/site/pages/en/learn/diagnostics/flame-graphs.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,9 +34,9 @@ Now let's get to work.
34
34
2. Try running `perf` - it might complain about missing kernel modules, install them too
35
35
3. Run node with perf enabled (see [perf output issues](#perf-output-issues) for tips specific to Node.js versions)
36
36
37
-
```
38
-
perf record -e cycles:u -g -- node --perf-basic-prof --interpreted-frames-native-stack app.js
39
-
```
37
+
```bash
38
+
perf record -e cycles:u -g -- node --perf-basic-prof --interpreted-frames-native-stack app.js
39
+
```
40
40
41
41
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
0 commit comments