I run 6.12.33m on SETI@home, Rosetta, and ClimatePrediction. On the curent and previous releases of BOINC, have experienced an issue where one or two of the projects complete all downloaded WUs, but the third project still has plenty of WUs left, so BOINC will not request more for the projects without any downloaded. For example at the moment, have yesterda run out of ClimatePrediction and Rosetta, but at that time had a couple of S@H WUs left. BOINC did not request more WUs for Rosetta when it ran out, likewise for CPDN. however when BOINC only had S@H left, it requested more S@H WUs. I now have 300 hours of processing in the queue for S@H only. My settings specify connect every 3 days, keep extra 5 days. I do this because on regular intervals one or other project runs out of available WUs (sometimes more than one). My other settings are that my %shares are 50% rosetta, 25% S@H and 25% CPDN. My current average work done for the three (normalised) is 35% rosetta, 40% S@H and 25% CPDN. My Rosetta is well under the target, and S@H is well over, So why does BOINC feel the need for more S@H WUs but not rosetta? Deadlines are not cutting in, nothing runs at high priority.

---

squeak

Because when BOINC tries, but fails, to obtain work from a project, it understands that the project server maybe under stress of some kind.

Rather than adding to the stress by repeated requests for work, it backs off the work request rate to the project(s) having difficulty keeping up, and asks another project to top up your cache instead. The longer the project problems which result in "can't supply work" go on, the less your machine will pester it.

But your machine will still ask roughly once a day: in effect "have you sorted out your problems yet?". If that request receives work, then you're back in business: if it doesn't, your computer keeps quiet for another day until trying again.

Aithough BOINC tracks your relative work across projects, and tries to obey your preferences in the long term, that isn't the most important factor in its decision-making process. Making allowance for projects with unreliable or overstretched servers (of which there seem to be an increasing number these days) is also important.

OK, that's good. But my problem at the moment is not that the projects are unable to supply WUs, but rather that BOINC does not feel the need to ask for them. It hasn't asked for them for Rosetta or CPDN for at least a week.

---

squeak