-
Notifications
You must be signed in to change notification settings - Fork 444
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
Seperate cpu options for active/idle #202
Comments
Commented by Nicolas on 7 Mar 37393735 23:33 UTC |
Commented by Nicolas on 11 Jul 37428399 04:26 UTC |
Commented by KSMarksPsych on 17 Sep 37436380 15:06 UTC |
Commented by evandro on 30 Jul 37436445 18:13 UTC It's not a problem with Windows, which runs BOINC threads only when there's no other thread to run, but it is in Linux, and possibly in OSX too, which gives BOINC threads a fair amount of CPU in spite of their low priority (typically 5% in a loaded system), when running BOINC always costs something. But this option would probably make more sense if how BOINC understands idle is changed. IIRC, BOINC considers only user interactivity to determine if a system is idle. This is probably fine with Windows because of the reason state above, but in Linux it would probably be a better option if in addition to user activity the system load were also considered to determine if other processes are running too. Nevertheless, such a change would also make sense on SMP desktops, always becoming more and more common with the launch of multi-core processors. I understand that there might be difficulties on implementing this depending on how many WU queues there are. If it's a single queue with the number of allowed CPUs determining how many can be active, it shouldn't be too hard. But if there are as many queues as allowed CPUs, it would be significantly harder. One might say that it would suffice to limit the number of CPUs that BOINC can use in a production system, but then when the system is idling BOINC performance could be greater. |
Commented by evandro on 25 May 37461364 19:06 UTC
All Unix variations provide soemthing equivalent. Unfortunately, Windows doesn't; the closest thing being querying the run-queue length or using the expensive system performance counters. |
This looks like it's the same thing that's asked in #41, so closing this as duplicate. |
Reported by wwhite81 on 24 Nov 37393303 20:00 UTC
Idea: Being able to set the max cpu load separately for active and idle running the same way you can for memory usage settings. Would allow the user to change from idle to cpu intensive tasks where max load causes issues without having to change the max load manually each time, with the chance to forget to ramp it back up once done and waste cpu time.
Migrated-From: http://boinc.berkeley.edu/trac/ticket/203
The text was updated successfully, but these errors were encountered: