Seti@Home optimized science apps and information
Optimized Seti@Home apps => Discussion Forum => Topic started by: Raistmer on 04 Aug 2009, 07:22:03 pm
-
LOG:
05/08/2009 03:16:58 [wfd] ------- start work fetch state -------
05/08/2009 03:16:58 [wfd] target work buffer: 604800.86 sec
05/08/2009 03:16:58 [wfd] CPU: shortfall 2229714.42 nidle 0.00 est. delay 34615.90 RS fetchable 100.00 runnable 100.00
05/08/2009 03:16:58 Einstein@Home [wfd] CPU: fetch share 1.00 debt -5217618.87 backoff dt 0.00 int 0.00 (overworked)
05/08/2009 03:16:58 Milkyway@home [wfd] CPU: fetch share 0.00 debt 0.00 backoff dt 0.00 int 0.00 (comm deferred)
05/08/2009 03:16:58 SETI@home [wfd] CPU: fetch share 0.00 debt -1703310.24 backoff dt 0.00 int 0.00 (comm deferred) (overworked)
05/08/2009 03:16:58 SETI@home Beta Test [wfd] CPU: fetch share 0.00 debt 0.00 backoff dt 0.00 int 0.00 (susp via GUI) (no new tasks)
05/08/2009 03:16:58 Einstein@Home [wfd] overall_debt -5217619
05/08/2009 03:16:58 Milkyway@home [wfd] overall_debt 0
05/08/2009 03:16:58 SETI@home [wfd] overall_debt -1703310
05/08/2009 03:16:58 SETI@home Beta Test [wfd] overall_debt 0
05/08/2009 03:16:58 [wfd] ------- end work fetch state -------
Currently work buffer definitely smaller than 6 days and it's impossible to get it filled from MW.
Will BOINC try to fill cache from other projects even if they are overworked or will keep cache almost empty ?
-
Comm Deferred means it won't even try until the site specified defer time expires.
I'm not having any problems getting work with MW using 3.3.38
3.3.36 always gets "(won't finish in time)"
-
Comm Deferred means it won't even try until the site specified defer time expires.
I'm not having any problems getting work with MW using 3.3.38
3.3.36 always gets "(won't finish in time)"
I suppose 6.6.36 and 6.6.38.
I reverted to 6.6.20 after few days experiments with 6.6.36&38.