| 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: 2
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I've noticed that some of my most recent tasks are suddenly reporting that they are going to take 30-45 hours to complete, but my system is managing it in 9.
Anyone got any ideas why this is? I have overclocked my system, but the dramatic difference makes that irrelevant (I think). Rob |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
The header of a task gets an estimated amount of flops that the project averaged in the previous couple days. Because the actual flops vary allot, you'l see for CEP large run time variations. My last 2 on same client, both validating, both having close credit claim with the quorum partner were 7 respectively 45 hours. We'll have to live with that until, if ever the techs figure out another statistical method to better project a batch's run time.
----------------------------------------Sowwy PS: There is an FAQ in the Start Here forum that helps to compute by hand a better estimate, but that only works after the job has run for a while.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Jan 26, 2009 2:14:18 PM] |
||
|
|
|