| 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: 14
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
4.2 to 3.8 was done about 2 weeks ago..
wcg is the ONLY project the tasks i am getting ar reporting some erronious finish times.. 60 80 90 and even more hours.. for instance a (cep) was reporting 131 hours to complete.. task finished in bout 4 hours... |
||
|
|
Bugg
Senior Cruncher USA Joined: Nov 19, 2006 Post Count: 271 Status: Offline Project Badges:
|
Rob, then I misunderstood how that DCF works in that case. I think I get it now. :) Thanks.
----------------------------------------![]() i5-12600K (3.7GHz), 32GB DDR5, Win11 64bit Home |
||
|
|
KWSN - A Shrubbery
Master Cruncher Joined: Jan 8, 2006 Post Count: 1585 Status: Offline |
4.2 to 3.8 was done about 2 weeks ago.. wcg is the ONLY project the tasks i am getting ar reporting some erronious finish times.. 60 80 90 and even more hours.. for instance a (cep) was reporting 131 hours to complete.. task finished in bout 4 hours... In that case some work unit that you ran took way longer than the server expected. This plays havoc with the DCF. Short of hacking the BOINC files, it will take care of itself as other results finish with more appropriate run times. Give it a day or so and you'll be back to normal again. ![]() Distributed computing volunteer since September 27, 2000 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
its almost back to normal now..
only 1 wu gfam saying 23 hrs. the rest are less that an hour to 5 or 6.. ty to all who tried to help..... |
||
|
|
|