Skip to content

chore: disable incremental compilation and trim debug info for dev builds #581

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

Open
vsbuffalo wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: disable incremental compilation and trim debug info for dev builds #581

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
37 changes: 37 additions & 0 deletions rust/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,43 @@ ir = { path = "crates/ir" }
# because it's in the same workspace.
external-harness = { path = "crates/external-harness" }

# Dev profile: incremental OFF, minimal debug info.
#
# This deviates from Cargo's defaults (incremental = true, debug = 2) on
# measured evidence, not preference. On macOS this workspace drove the
# incremental cache into a pathological state: `target/debug/incremental` and
# `target/debug/deps` reached 44 GB each, ~1.67M files in one directory, and
# every one of those Mach-O artifacts is assessed by `syspolicyd` (Gatekeeper),
# which saturated at ~70% of a core. A debug `cargo test` took 6m52s at 4% CPU;
# the same work with incremental disabled took 19s at 471% CPU. Nothing was
# compute-bound — the build was waiting on filesystem/security assessment.
#
# Incremental compilation is a good trade in the normal regime: more files for
# faster edit-compile cycles. This workspace is outside it, and the cache is
# making compilation dramatically worse rather than better.
#
# `line-tables-only` for our crates and no debug info for dependencies is
# Cargo's own build-performance recommendation: panic backtraces still resolve
# to source locations, without paying for full DWARF. `split-debuginfo` is left
# at the macOS default (`unpacked`) deliberately — `packed` runs `dsymutil` on
# every build, and with debug info this reduced there is little left to pack.
# Benchmark before changing it.
#
# For LLDB-quality debugging use the `debugging` profile below rather than
# making every agent and CI build carry metadata it does not need.
[profile.dev]
incremental = false
debug = "line-tables-only"

[profile.dev.package."*"]
debug = false

# Full DWARF when you actually need a debugger:
# cargo build --profile debugging
[profile.debugging]
inherits = "dev"
debug = 2

# Profiling profile: release-grade codegen + line tables so `samply`/`perf`
# can resolve symbols and source lines. Kept separate so the shipped
# `release` profile stays lean. Build with `cargo build --profile profiling`.
Expand Down
Loading