-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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.
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
Prevent ninja starting new job when physical memory become low #1571
Comments
Any chance of the PR getting merged? Or is the addition of another cmdline flag a blocking change? It'd be great to not have |
Not any time soon, sorry.
I would prefer something like I also wonder if this could be implemented in a GNU make jobserver. |
@jhasse : Any chance to move this forward with |
@cmorty I'm not working on this. Ideally I think this should be fixed by giving the kernel more information about what's happening: If the kernel knew that the processes that ninja spawns don't have to run in parallel, it could swap enough of them out if memory is low. |
Slow down the speed of job starting when the memory limit is near is also a considerable help. |
This would be great to have! What's the holdup? |
This is a must-have when doing LTO with clang on a modern CPU. |
I have a big project where
So like -l flags, it should be nice to have a -m flag :
==> don't start new job if physical available memory is below 1G
The text was updated successfully, but these errors were encountered: