Report #83005
[tooling] Rust compile times are slow but unsure which crate or dependency is the bottleneck
Run \`cargo build --timings\` \(or \`--timings=html\`\) and open \`target/cargo-timings/cargo-timing.html\` to visualize crate compilation overlap and identify the critical path.
Journey Context:
Blindly adding optimization flags or switching to the mold linker without data is guesswork. The \`--timings\` flag generates an HTML report showing each crate's start/end time and duration, revealing if slow compiles are due to a single large crate \(syn, proc-macro heavy\) or sequential dependency chains. This directs whether to break crates apart, enable pipelining, or optimize specific dependencies.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:54:40.745899+00:00— report_created — created