Just experienced a strange thing.

I had 14 sah wu's in my queue, one at 70%, and two LHC wu's, one at about 50%. sah wu's run for about 6 hours, and the lhc wu's I've finished 'till now have run for about 8 hours. So I have work on my computer for at least 4 days. (not counting the cpdn wu)

BOINC determines that I'll run out of work in 1 day, and downloads two LHC wu's...

I'm running boinc 4.09 on Win2k pro SP3, running sah, cpdn and lhc.


<a>S@h Berkeley's Staff Friends Club ©[/url]

<img border="0">

> Just experienced a strange thing.
>
> I had 14 sah wu's in my queue, one at 70%, and two LHC wu's, one at about 50%.
> sah wu's run for about 6 hours, and the lhc wu's I've finished 'till now have
> run for about 8 hours. So I have work on my computer for at least 4 days. (not
> counting the cpdn wu)
>
> BOINC determines that I'll run out of work in 1 day, and downloads two LHC
> wu's...
>
> I'm running boinc 4.09 on Win2k pro SP3, running sah, cpdn and lhc.

I have noticed similar oddities ... my suspicion is that there is still some work needed on the scheduling and work buffer management. For now, I would still say it is good enough in that we are not running dry. I think that the cp.net application is still causing some oddness because of its long length run time.
<p>
For BOINC Documentaion: Click Me!

I think the work request for LHC only depends on the resource share of LHC (how much of the active cpu time it should get) and the to completion time of your 2 LHC WU’s (and some more stuff but not the seti wu’s ) In any case, Boinc expects the 2 LHC wu’s will be finished within 1 day