Optimizing Build Performance

Cargo configuration options and source code organization patterns can help improve build performance, by prioritizing it over other aspects which may not be as important for your circumstances.

Same as when optimizing runtime performance, be sure to measure these changes against the workflows you actually care about, as we provide general guidelines and your circumstances may be different, it is possible that some of these approaches might actually make build performance worse for your use-case.

Example workflows to consider include:

• Compiler feedback as you develop (cargo check after making a code change)
• Test feedback as you develop (cargo test after making a code change)
• CI builds

Cargo and Compiler Configuration

Cargo uses configuration defaults that try to balance several aspects, including debuggability, runtime performance, build performance, binary size and others. This section describes several approaches for changing these defaults that should be designed to maximize build performance.

You can set the described options either in the Cargo.toml manifest, which will make them available for all developers who work on the given crate/project, or in the config.toml configuration file, where you can apply them only for you or even globally for all your local projects.

Reduce amount of generated debug information

Recommendation: Add to your Cargo.toml or .cargo/config.toml:

[profile.dev]
debug = "line-tables-only"

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

[profile.debugging]
inherits = "dev"
debug = true

This will:

• Change the dev profile (default for development commands) to:
  • Limit debug information for workspace members to what is needed for useful panic backtraces
  • Avoid generating any debug information for dependencies
• Provide an opt-in for when debugging via --profile debugging

Trade-offs:

• ✅ Faster build times
• ✅ Faster link times
• ✅ Smaller disk usage of the target directory
• ❌ Requires a full rebuild to have a high-quality debugger experience

Use an alternative codegen backend

Recommendation:

• Install the Cranelift codegen backend rustup component

  $ rustup component add rustc-codegen-cranelift-preview --toolchain nightly
  

• Add to your Cargo.toml or .cargo/config.toml:

  [profile.dev]
  codegen-backend = "cranelift"
  

• Run Cargo with -Z codegen-backend or enable the codegen-backend feature in .cargo/config.toml.
  • This is required because this is currently an unstable feature.

This will change the dev profile to use the Cranelift codegen backend for generating machine code, instead of the default LLVM backend. The Cranelift backend should generate code faster than LLVM, which should result in improved build performance.

Trade-offs:

• ✅ Faster code generation (cargo build)
• ❌ Requires using nightly Rust and an unstable Cargo feature
• ❌ Worse runtime performance of the generated code
  • Speeds up build part of cargo test, but might increase its test execution part
• ❌ Only available for certain targets
• ❌ Might not support all Rust features (e.g. unwinding)

Enable the experimental parallel frontend

Recommendation: Add to your .cargo/config.toml:

[build]
rustflags = "-Zthreads=8"

This rustflags will enable the parallel frontend of the Rust compiler, and tell it to use n threads. The value of n should be chosen according to the number of cores available on your system, although there are diminishing returns. We recommend using at most 8 threads.

Trade-offs:

• ✅ Faster build times
• ❌ Requires using nightly Rust and an unstable Rust feature