diff options
| author | Niko Matsakis <niko@alum.mit.edu> | 2018-09-07 11:01:29 -0400 |
|---|---|---|
| committer | Who? Me?! <mark-i-m@users.noreply.github.com> | 2018-09-10 19:25:29 -0500 |
| commit | 90bac20aa75203e5a20f2e0f8e51ad42974624fc (patch) | |
| tree | 78fdb5a6c64f3c1be2430abbeab9cbca3cb401f9 /src/doc/rustc-dev-guide | |
| parent | 1bd737675aa3a8c29a8eb660bdde9e2500a6ed4e (diff) | |
| download | rust-90bac20aa75203e5a20f2e0f8e51ad42974624fc.tar.gz rust-90bac20aa75203e5a20f2e0f8e51ad42974624fc.zip | |
update with njn's insight
Diffstat (limited to 'src/doc/rustc-dev-guide')
| -rw-r--r-- | src/doc/rustc-dev-guide/src/profiling/with_perf.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/src/doc/rustc-dev-guide/src/profiling/with_perf.md b/src/doc/rustc-dev-guide/src/profiling/with_perf.md index 683b61d2e1e..cec17d344ea 100644 --- a/src/doc/rustc-dev-guide/src/profiling/with_perf.md +++ b/src/doc/rustc-dev-guide/src/profiling/with_perf.md @@ -30,11 +30,11 @@ perf record -F99 --call-graph dwarf XXX ``` The `-F99` tells perf to sample at 99 Hz, which avoids generating too -much data for longer runs (why 99 Hz you ask? No particular reason, it -just seems to work well for me). The `--call-graph dwarf` tells perf -to get call-graph information from debuginfo, which is accurate. The -`XXX` is the command you want to profile. So, for example, you might -do: +much data for longer runs (why 99 Hz you ask? It is often chosen +because it is unlikely to be in lockstep with other periodic +activity). The `--call-graph dwarf` tells perf to get call-graph +information from debuginfo, which is accurate. The `XXX` is the +command you want to profile. So, for example, you might do: ``` perf record -F99 --call-graph dwarf cargo +<toolchain> rustc |