| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Estimated Time to Completion is huge - resolved |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
tmedve
Senior Cruncher USA Joined: Nov 16, 2004 Post Count: 182 Status: Offline Project Badges: 
|
Recently my estimated time to completion in Boinc manager is very large before the job starts running. For a job that actually runs in an hour, the initial estimate is around 12 hours. Does not effect the actual running of the job, but it messes up the number of jobs that go into the hopper. I am running i5 chip with 4 threads, Boinc version 6.10.58.
----------------------------------------It ran correctly for a long time UNTIL I put some "waiting to run" jobs on "suspend" so that some Betas would run first. Then, when I "resumed" those jobs, the timed estimate got dorked. I had hoped that running for a while would fix it, but it has been over a day and times are still high. I also rebooted the entire machine a couple of times with no effect, Any suggestions on how to get the estimated completion time back to normal? Thanks. Tom  [Edit 1 times, last edit by tmedve at Nov 6, 2013 2:46:49 PM] |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7668 Status: Offline Project Badges: 
|
Just wait a couple of days. If you have too many WU's, lower your cache setting for awhile.
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Recently my estimated time to completion in Boinc manager is very large before the job starts running. For a job that actually runs in an hour, the initial estimate is around 12 hours. Does not effect the actual running of the job, but it messes up the number of jobs that go into the hopper. I am running i5 chip with 4 threads, Boinc version 6.10.58. It ran correctly for a long time UNTIL I put some "waiting to run" jobs on "suspend" so that some Betas would run first. Then, when I "resumed" those jobs, the timed estimate got dorked. I had hoped that running for a while would fix it, but it has been over a day and times are still high. I also rebooted the entire machine a couple of times with no effect, Any suggestions on how to get the estimated completion time back to normal? Thanks. Tom Upgrade to 7.2.27 [release candidate], and those TTC super inflations and shrinks disappear. It's because then the blocking of the client DCF feature kicks in [the client has only 1 DCF for WCG]. This blocking is instructed by the v701 WCG BOINC servers, and enforces a 1.000000 factor. From that point on, new work assumes the individual science runtime average FPOPS as calculated on the servers. To repeat, at a science level, meaning if something goes wrong with the BETA average, it does not affect the FAAH or CEP2, and buffer explosion/implosion is limited. [Edit 1 times, last edit by Former Member at Nov 6, 2013 8:37:46 AM] |
||
|
|
|