Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 1
|
![]() |
Author |
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
When a client has been off for longer, or scheduling projections have led to very long estimated return times, further out then the deadline of the chosen projects, work will not be sent to these clients, sometimes up to a point where cached work has been whole or partly completed. When the condition arises, a signal will be recorded in the BOINC message log, similar to the sample below:
----------------------------------------22-01-2010 14:44:37 World Community Grid Message from server: (won't finish in time) Computer on 41.1% of time, BOINC on 86.7% of that Whilst BOINC from later 6.10 versions is much better at handling these conditions [to include ignoring periods when the client has been off for longer then 10 days], it could still occur. Restoring the client to a condition of work fetch can be achieved by leaving the computer on for longer so BOINC thinks there's more time to work on the science and eventually some will be retrieved, but that's not very satisfying, let alone an energy friendly way. There is a workaround to quickly fix the problem:
This should rebuild the time keeping statistics back to their standard settings as were it a new install. Within a brief period tasks should be fetched again for the projects that are allowed to. Related topics: Reporting x completed tasks, not requesting new tasks [sched_op_debug] CPU work request: 0.00 seconds; 0.00 idle CPUs
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
![]() |