% of processor per project
2 Dec 2005 1:14:31 UTC
Topic 190274
(moderation:
I thought there was supposed to be a way to apportion the amount of processor time on a project. I want to allow 25% processor cycles to each of 2 projects leaving 50% of the processor cycles free. Does anyone have a solution.
Please reply to
Thanks
Lorne
% of processor per project
)
Lorne,
You seem to have misunderstood the apportionment. Boinc will indeed allot time to the various projects in the ratio you choose, meaning that project A would get the same amount of time as Project Z as long as the ratio is 1-to-1 (25/25 or 55/55 or 342/342). Unless you run Boinc on a multiprocessor computer, only 1 project will be processed at a time, Boinc will switch off from one project to another at intervals set by your preferences.
The only way I've heard of limiting CPU usage on a processor is an app called "threadmaster". NOTE: I have never used this app, have no direct knowledge of it, and don't know where to get it, but Google is your friend.
Respects,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: I want to allow 25%
)
Hi Lorne,
Welcome to the Einstein@Home project. We hope you enjoy your stay here.
Although you asked for a reply to your private email address, we know that many people skim these boards and pick up much valuable information by reading answers to questions. I hope you don't mind if we share our answers like this.
I'd just like to add a little more to Michael's answer. Please realise that BOINC runs the science applications for the various projects at very low priority so that your own use of your computer is not compromised. If you were able to limit BOINC to 50% of your total cycles, the system idle process would get most of the other 50% anyway. Unless you are concerned about temperature issues, say on a laptop for example, it's usually quite safe to just let BOINC use whatever you don't need for your own use. BOINC gets out of the way very well when you do need to run something else for yourself.
Cheers,
Gary.