People have modified the client before to get more work, so having an extra safety option is a good idea, I think. On the other hand, they can remove the code to send task listings, too... Back to the original issue - scheduler from server_stable is only sending 1 task per request. Was it changed to take CPU count into account later?
2009/9/21 Nicolás Alvarez <[email protected]> > El Lunes 21 Sep 2009 01:37:55 David Anderson escribió: > > Rytis Slatkevičius wrote: > > > I'm not sure if that is related, but after the update server started > > > sending 2 tasks, while config.xml has max_wus_in_progress = 1, > > > max_wus_to_send = 1. We only need one task to be sent, as we're > > > non-cpu-intensive: > > > > The problem is that max_wus_in_progress gets multiplied by the # of CPUs. > > One way around this is to include <max_ncpus>1</max_ncpus>. > > Kind of a kludge. > > Carl, what do you do on QCN? > > -- David > > max_wus_in_progress is unneeded for non-CPU-intensive projects. It's enough > to > have max_wus_to_send=1. Once a task is sent, the client won't ask for more > until it's done. > > -- > Nicolas > _______________________________________________ > 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. > -- Rytis Slatkevičius +370 670 77777 ICQ 270359185; MSN [email protected]; GTalk [email protected]; Skype rytis.s (text only) _______________________________________________ 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.
