When I have my Predictor account running, updating my SETI account does not request work, even when their resources are set to 80%/20%.

Predictor active:
SETI@home - 2004-07-19 02:44:11 - Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-07-19 02:44:15 - Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-07-19 02:44:15 - Project prefs: no separate prefs for home; using your defaults

Predictor detached:
Predictor@home - 2004-07-19 02:44:34 - Detaching from project
--- - 2004-07-19 02:44:34 - Fewer active results than CPUs; requesting more work
SETI@home - 2004-07-19 02:44:34 - Requesting 86363 seconds of work
SETI@home - 2004-07-19 02:44:35 - Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-07-19 02:44:38 - Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded


I believe it should request work regardless of whether or not there are "Fewer active results than CPUs". Or is it a symptom of the number of WUs Predictor gets at once?

My guess is that you have been running S@H for a few days/weeks. A new project will dominate work requests until it has caught up in recent average CPU usage. This can take up to a month depending upon how long you have been running the old projects, the resource shares, and WU availability. The less time that you have been running the old project(s) the shorter the ramp up. The lower the resource share of the new project, the shorter the ramp up. The lower the WU availibility for the new project, the longer the ramp up.

I actually have no work completed for S@H on BOINC, because of the lack of WUs available.