Opened 18 years ago
Last modified 13 years ago
#41 reopened Enhancement
differentiate between number of CPUs to use in idle and busy mode
Reported by: | KSMarksPsych | Owned by: | davea |
---|---|---|---|
Priority: | Minor | Milestone: | Undetermined |
Component: | Client - Daemon | Version: | 6.10.58 |
Keywords: | Cc: | Pepo |
Description
Posted by: Date: 3:05 PM 04-07-2007 BOINC detects if the machine is busy and can limit the number of CPUs to use. I'd like to see a feature, that I can define 2 numbers of CPUs to use, one if the machine is idle and one if the machine is busy. Right now I've got a dual processor machine and allow BOINC to use one of them so that my work is not slowed down. But when the machine is idle, BOINC could use both CPUs. Right now, this is not possible. With the advent of multi-processor/core machines spreading out to end users, this would allow more CPU power to be used by BOINC and the necessary preconditions are already implented.
Change History (6)
comment:1 Changed 18 years ago by
Component: | Client - Manager → Client - Daemon |
---|---|
Owner: | changed from romw to davea |
Priority: | Trivial → Minor |
comment:2 Changed 18 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I'm not in favor of this. I don't think limiting the number of CPUs used while busy will increase system responsiveness. Limiting the RAM usage will.
E.g.: if you use 1 CPU and it causes thrashing, your system will be sluggish. If you use N CPUs (at zero priority) with small working set, your system will not be sluggish
comment:3 Changed 16 years ago by
Cc: | Pepo added |
---|---|
Resolution: | wontfix |
Status: | closed → reopened |
According to numerous requests, I'd like to suggest this being implemented arbitrarily. Currently the client considers just whether to go or sleep and how much memory to use, according to user's idleness.
Both Working and Idle states should contain a separately manageable set of "resources usage preferences" (CPU % throttling, %/number of CPU cores, memory usage, exclusive_app, etc.) just like it is now with preference sets for venues.
comment:5 Changed 14 years ago by
Version: | → 6.10.58 |
---|
This way of managing BOINC preferences gets requested multiple times a year, again and again and again... Thus, let's not forget the proposal from a year ago. And best wishes to the related followup discussions.
What do you think?