Skip to content

Commit 85ed2e3

Browse files
nikomatsakismark-i-m
authored andcommitted
update with njn's insight
1 parent 9a463df commit 85ed2e3

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

src/profiling/with_perf.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -30,11 +30,11 @@ perf record -F99 --call-graph dwarf XXX
3030
```
3131

3232
The `-F99` tells perf to sample at 99 Hz, which avoids generating too
33-
much data for longer runs (why 99 Hz you ask? No particular reason, it
34-
just seems to work well for me). The `--call-graph dwarf` tells perf
35-
to get call-graph information from debuginfo, which is accurate. The
36-
`XXX` is the command you want to profile. So, for example, you might
37-
do:
33+
much data for longer runs (why 99 Hz you ask? It is often chosen
34+
because it is unlikely to be in lockstep with other periodic
35+
activity). The `--call-graph dwarf` tells perf to get call-graph
36+
information from debuginfo, which is accurate. The `XXX` is the
37+
command you want to profile. So, for example, you might do:
3838

3939
```
4040
perf record -F99 --call-graph dwarf cargo +<toolchain> rustc

0 commit comments

Comments
 (0)