Skip to content- Sources: primary, discussion
- Summary: Since nightly-2026-11-14 the rustc frontend runs in parallel by default with 2 threads, set with -Zunstable-options --jobs-frontend=N. With 8 threads the team measured a 44% mean wall-time cut for single-crate cargo check, but only about 15% end to end on checking the whole cargo crate graph on an 8-core machine and 3 to 5% on incremental rebuilds. Diagnostics order can be nondeterministic and some reproducibility bugs remain, and stable is unchanged.
- Why it matters: Teams on nightly can test higher frontend thread counts for faster checks, and should report crashes or non-reproducible binaries before stabilization.
- Background: The rustc frontend covers parsing, macro expansion, name resolution, type checking and borrow checking, and has run on one thread while LLVM codegen ran in parallel. Opt-in parallel frontend support reached nightly three years ago with a 2024 stabilization goal that slipped.