From 940438217c9b33fe0ce1fe1eb7cb41c336b6e401 Mon Sep 17 00:00:00 2001 From: Thomas Eizinger Date: Wed, 18 Dec 2024 14:01:23 +0100 Subject: [PATCH] docs(rust): fix profiling command (#7547) Signed-off-by: Thomas Eizinger --- rust/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rust/README.md b/rust/README.md index 527132f95..61f771d42 100644 --- a/rust/README.md +++ b/rust/README.md @@ -34,7 +34,7 @@ The recommended way for benchmarking any of the Rust components is Linux' `perf` For example, to attach to a running application, do: 1. Ensure the binary you are profiling is compiled with the `release` profile. -1. `sudo perf perf record -g --freq 10000 --pid $(pgrep )`. +1. `sudo perf record -g --freq 10000 --pid $(pgrep )`. 1. Run the speed test or whatever load-inducing task you want to measure. 1. `sudo perf script > profile.perf` 1. Open [profiler.firefox.com](https://profiler.firefox.com) and load `profile.perf`