Collateral damage caused by SETI server hang :(
Anonymous
21 Feb 2005 10:49:28 UTC
Topic 12625
(moderation:
> As the title states there is a very bad bug in the BOINC CC:
>
> Since the SETI server nearly constantly ignores requests for work at the
> moment my clients start to suck up units from Einstein (at least one Einstein
> unit for every unresponded request to SETI). The queue with Einstein units is
> now nearly too big for the completion time. When SETI comes back to life the
> client will suck SETI units and then won't be able to complete the Einstein
> units in time.
>
> This is a big bug in the concept! :(
> Can Einstein somehow slow down giving out work to clients, that aren't able to
> finish the work in time?
If the resource shares for SETI@Home and E@H are equal, then the scheduler should only send as much work as you can do in time t/2, where t is the time available for all BOINC work. But if the core client is not handing this resource share fraction correctly to the scheduler, then you'll get time t instead. Can you review your resource share fractions please?
Bruce
Collateral damage caused by SETI server hang :(
)
> Sorry, had some work to do...
>
> I have CC 4.19 and share is set to 50/50 Seti/Einstein and connect every 3
> days (meanwhile reduced to 1 day). After doing some math i think the problem
> lies herein:
> The BOINC CC estimates ~12.5 hrs per einstein unit where in reality it uses
> ~16 hrs on my 1000 Mhz Pentium III-M notebook.
Then reducing the cache to 2.34 days (3*12.5/16) should help adjust for this.
Cheers,
Bruce