[email protected] wrote: > OK, only during transfers. It looked like you were advocating something > completely else. Yes, with a queue of 0, and one project, there will be a > pause between tasks while a new task downloads. With multiple projects, > the decision was to possibly (depending on LTD) keep tasks from several > projects around - for variety.
Even for multiple attached projects, a user defined cache size of zero should ensure that there are never more WUs (waiting or active) than cores at any time. That is, there is zero cache. The 'variety' consideration can mean that WUs are downloaded from the projects in turn, but still there should never be anything more than one WU per core. > [email protected] wrote: >> Idle CPUs should not going to be a part of the design for small queues. >> Especially since the default queue is 0. > > For a RAM-only system, I will want there to be no more than exactly one > WU per core on the system at any instant. Hence, an idle CPU during > transfers is actually wanted. > > With a cache setting of zero, that should be the correct and expected > result. Regards, Martin -- -------------------- Martin Lomas m_boincdev ml1 co uk.ddSPAM.dd -------------------- _______________________________________________ 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.
