-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Closed as not planned
Labels
A-build-executionArea: anything dealing with executing the compilerArea: anything dealing with executing the compilerA-jobserverArea: jobserver, concurrency, parallelismArea: jobserver, concurrency, parallelismC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Description
When building rust-lang/rust in parallel, I found that rustc_middle would take the vast majority of the compilation time and memory. I repeatedly ran into the OOM-killer because cargo would start up three more things building in parallel, and rustc_middle was already using 5-6GB of my 8GB of RAM. I'd like to be able to somehow hint to Cargo that it should treat rustc_middle as particularly heavy to build, and that it should count as multiple "slots" in the 4 parallel jobs Cargo would allow to run. That would have allowed me to successfully build within 8GB of RAM.
ipatchEh2406 and Coldblackiceipatch
Metadata
Metadata
Assignees
Labels
A-build-executionArea: anything dealing with executing the compilerArea: anything dealing with executing the compilerA-jobserverArea: jobserver, concurrency, parallelismArea: jobserver, concurrency, parallelismC-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`