Skip to content
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

Jump to bottom

Hint mechanism to require more "slots" to build a crate #8405

Closed
joshtriplett opened this issue Jun 24, 2020 · 3 comments
Closed

Hint mechanism to require more "slots" to build a crate #8405

joshtriplett opened this issue Jun 24, 2020 · 3 comments
Labels
A-build-execution Area: anything dealing with executing the compiler A-jobserver Area: jobserver, concurrency, parallelism C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`

Comments

@joshtriplett
Copy link
Member

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.
@joshtriplett joshtriplett added the C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` label Jun 24, 2020
@ehuss ehuss added the A-jobserver Area: jobserver, concurrency, parallelism label Jun 25, 2020
@luser
Copy link
Contributor

luser commented Feb 9, 2021

Possibly a duplicate of #7437?

@epage epage mentioned this issue Apr 20, 2022
Open
@epage
Copy link
Contributor

epage commented Nov 2, 2023

#7437 is about package prioritization while this is about resource utilization.

@epage epage added the A-build-execution Area: anything dealing with executing the compiler label Nov 2, 2023
@weihanglo weihanglo mentioned this issue Nov 3, 2023
Open
@epage
Copy link
Contributor

epage commented Nov 3, 2023

#12912 discusses the OOM problem and is exploring smaller and bigger solutions. To keep the conversation in one place, I'm closing this.

@epage epage closed this as not planned Won't fix, can't repro, duplicate, stale Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-build-execution Area: anything dealing with executing the compiler A-jobserver Area: jobserver, concurrency, parallelism C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ehuss @epage @joshtriplett @luser