rad experiment show 4678dadfcc09e93b6174f3ed1f92d629e74b9217
by ee@did:key:z6MkvsiybCuk1WDZhh2aXDx7NTiZejKgWZygMNsUuXDMNvVQ · Apr 20 11:35 2026
Set `[profile.dev] debug = 0` to test whether lowering dev debuginfo speeds up clean cargo check.
Measurements
Metric
BaselineThe benchmark measurement of the unmodified code
CandidateThe code with the proposed optimization applied
Candidate/Parent ΔThe performance change from baseline to candidate
cargo_check_s (s)primary
Reduce the wall-clock time of a clean `cargo check --all` for this workspace on the current macOS host.
The benchmark represents edit-compile iteration speed for the Rust workspace, with emphasis on changes in `wgpu-native` and `wgpu-remote` source/layout that reduce compile work without breaking the build.
5.300 s (n=1)
5.839 s (n=1)
+10.16%REGRESSED
target_kbsecondary
80948.000 (n=1)
79564.000 (n=1)
-1.70%REGRESSED
Annotations
hypothesis
Even for `cargo check`, dev-profile debuginfo settings might add frontend work or metadata overhead; reducing debuginfo could improve iteration speed.
learned
Lowering dev debuginfo reduced artifact size but made clean `cargo check` slower on this workload.
next_action_hint
Focus on dependency graph and macro/proc-macro sources of work instead of profile flags.
rollback_reason
The clean check benchmark regressed materially despite a smaller target directory, so debuginfo generation was not the dominant cost here.
Base CommitThe starting commit before the optimization was applied