Exploring Crate Graph Build Times with `cargo build -Ztimings`

bjorn3 · September 21, 2019, 8:50am

You could place a cargo.arg("-Ztimings"); after

rust-lang/rust/blob/5349e69ae207c4d11245e75463c091eded3ad13c/src/bootstrap/builder.rs#L756


/// rustc compiler, its output will be scoped by `mode`'s output directory,
/// it will pass the `--target` flag for the specified `target`, and will be
/// executing the Cargo command `cmd`.
pub fn cargo(
    &self,
    compiler: Compiler,
    mode: Mode,
    target: Interned<String>,
    cmd: &str,
) -> Command {
    let mut cargo = Command::new(&self.initial_cargo);
    let out_dir = self.stage_out(compiler, mode);


    // Codegen backends are not yet tracked by -Zbinary-dep-depinfo,
    // so we need to explicitly clear out if they've been updated.
    for backend in self.codegen_backends(compiler) {
        self.clear_if_dirty(&out_dir, &backend);
    }


    if cmd == "doc" || cmd == "rustdoc" {
        let my_out = match mode {

That will pass -Ztimings to every cargo invocation performed by ./x.py.

Topic		Replies	Views
Help us benchmark incremental compilation!	48	12011	March 25, 2019
Cargobomb report stable v. nightly 2017-03-14	3	955	March 25, 2019
[Pre-RFC] Caching improvements and system-wide crate cache cargo	1	763	June 18, 2020
Slow Linking with External Crates (trying to investigate internal cause)	3	912	March 25, 2019
New 'cargotest' builders for CI will keep Rust working better	8	3118	March 25, 2019

Exploring Crate Graph Build Times with `cargo build -Ztimings`

Related Topics