Skip to content

cargo timings has been stabilized #1319

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 28, 2022
Merged

cargo timings has been stabilized #1319

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7392ba3
cargo timings has been stabilized
ehuss Feb 26, 2022
e389a5a
Update src/profiling.md
pierwill Feb 28, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/profiling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,9 @@ Depending on what you're trying to measure, there are several different approach
full-featured graphical interface.

- If you want a nice visual representation of the compile times of your crate graph,
you can use [cargo's `-Z timings` flag](https://doc.rust-lang.org/cargo/reference/unstable.html#timings),
eg. `cargo -Z timings build`.
You can use this flag on the compiler itself with `CARGOFLAGS="-Z timings" ./x.py build`
you can use [cargo's `--timings` flag](https://doc.rust-lang.org/nightly/cargo/reference/timings.html),
e.g. `cargo build --timings`.
You can use this flag on the compiler itself with `CARGOFLAGS="--timings" ./x.py build`

- If you want to profile memory usage, you can use various tools depending on what operating system
you are using.
Expand Down