-
Notifications
You must be signed in to change notification settings - Fork 447
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
allow Boinc to use a variable number of cores #1590
Comments
I don't understand when to use a stepwise reduction on cpu load? Do you want something that is described in #41? |
rather, on multi-core systems: |
This is what already happens because science apps have the lowest priority. What the suspend eliminates is disk IO, that the user may need for something else and the need for the OS scheduler to consider low priority processes when scheduling cpu runtime. So I'm not quite sure what the advantages of the stepwise reduction is compared to just setting a higher value and complete suspension. Asked another way: What's the overhead from having |
It just seemed to me a more intuitive way of doing things. |
I think more general approach in #41 is better. |
On multi-core cpu's allow the user to specify both the minimum and maximum number of cores available to Boinc.
The idea is to allow Boinc to reduce its cpu-load in a stepwise rather than all-or-nothing manner.
The text was updated successfully, but these errors were encountered: