How many WUs are downloaded depends on the number of projects you are attached to and the resource shares for those projects. 4.05 will only download one WU from a project with a long deadline if that project has less than 50% of the total resource share.

It does seem to do somewhat better at getting the resource shares right with more projects. I have a dual where the shares are 50:10:10 for three projects. The project with 50 gets a CPU all to itself, and the other two swap on the other processor. However, the total is 50:50:50:10:10:10:.0001 of all the projects that it is attached to.

I have pointed out the problems with slow machines, deadlines, odd resource shares, and CPU starvation to the developers. Hopefully this will be fixed in a future version.

CPU Scheduling in Ver 4.05



M7 Seti@h Berkeley's Staff Friends Club ©

> Mr. J. McLeod VII,
>
> Thank you, again, for a reply. I shall await Predictor@Home's upgrade to see
> if I can get the same results as you with the 3 projects running.
>
> I assume, that as there are only 2 projects using Boinc 4.0x, at the moment,
> your referral to the 50/10/10 time-slice was when all 3 projects were still on
> Boinc 3.1x-3.2x.
>
> As the CPDN Beta calculation shall take somewhere between, 35 - 40 days on my
> machine (all my Alpha calculations crashed at some point - usually towards the
> end); I likely will detach Seti- & Predictor@Home from my P4-HT as is
> would be, in my opinion, ludicrous to increase the CPDN calculation length to
> 4+ months from 5 weeks.
>
> -H. Richard Utzig
>
Actually, no, there is also the BOINC Alpha test (by invitation only). I was referring to 3 4.x projects. The other included the 3 3.x projects i am attached to.

/edit
The machine that was having the problem was going to take 2 years to complete the CPDN WU with out interruption. It is still running as a test, but I have asked them to reissue it.

Client scheduling policies



M7 Seti@h Berkeley's Staff Friends Club ©