Project preferences would work well. The main resource problem is memory usage. There are projects that use up to 2GB of main memory/WU. You can see how that can soon become a problem with 4, 6, 8 & 12 core CPUs. To make things worse, 32bit OSes only allow ~3GB of main memory.
Regards/Ed On Wed, Sep 22, 2010 at 8:23 AM, <[email protected]> wrote: > Still better would be to do it automatically based on resource usage. > > jm7 > > > > Peter Slacik > <peter.b.sla...@g > mail.com> To > Ed A <[email protected]> > 09/22/2010 09:18 cc > AM [email protected], > [email protected], boris > mouradian <[email protected]> > Subject > Re: [boinc_dev] option to choose > the number of CPU cores to each > project > > > > > > > > > > > The most "user-friendly" option would be to limit the number of used > cores (max. number of active tasks (or threads)) according to particular > project's user preferences - either per-project or per-application. And > at best separately in each venue... > > > Peter Slacik > > > On Wed, 22 Sep 2010 08:06:21 -0500, Ed A wrote: > > There are projects however that we can't run on multi core CPUs because > the > > resource requirements are too high to allow more than 1 or 2 instances. > > This is getting to be more and more of a problem as the number of CPU > cores > > keeps increasing. Limiting the number of cores on these projects would > > allow us to participate. An "expert" option or even a switch in the > > cc_config.xml or app_info.xml would help. > > > > Regards/Ed > > > > > > On Wed, Sep 22, 2010 at 7:37 AM, <[email protected]> wrote: > > > > > >> 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 > >> > >> > > > > _______________________________________________ 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.
