Assigning a particular number of cores to each project is too rigid.
Sometimes projects cannot supply work, do we leave a CPU idle? Sometimes
work needs extra CPU time right now to finish on time. Do we let the work
return late and be worthless to the project? If we don't, do we break the
resource shares by not repaying the borrowed resource share or do we break
the CPUs / project setup by paying back the CPU time? Do we limit each
machine to no more than N projects where N is the number of CPUs? Some
tasks are multi threaded and run better if all CPUs on the system are
allocated to each task for the duration of the task. Do we not allow these
tasks?
The answers for all of these questions have fallen on the side against
rigidly assigning a number of CPU cores to each project.
jm7
boris mouradian
<[email protected]
om> To
Sent by: [email protected]
<boinc_dev-bounce cc
[email protected]
u> Subject
[boinc_dev] option to choose the
number of CPU cores to each project
09/21/2010 02:31
PM
Hello
I do not know if this is the right mailbox for this request, but would
anyone know why the option to choose the number of CPU cores to each
project
was not successful in developing boinc manager ?
thank you
_____________________________________
Vous n'utilisez pas la puissance de votre PC alors allez sur le site
suivant
et aidez la recherche merci :
http://www.boinc-af.org/ ou http://boincfrance.org/
You then do not use the power of your PC go on the following site and thank
you help research with software/piece of software BOINC on the site:
http://boinc.berkeley.edu/
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.