| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: The Clean Energy Project Forum
Thread: reboot causes longer run time |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 10
|
|
| Author |
|
|
dondee
Advanced Cruncher Joined: Jan 16, 2006 Post Count: 100 Status: Offline Project Badges: 
|
My computer rebooted for some reason and one of the wu now has 17:20 left to run. It has been running for 7:59. This the first time I have seen this, what has happened and should I abort this wu or run it out? I don't want to waste crunching time, especially now.
Average run time up to this point has been 6:46. Thanks for any help. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello dondee,
Hard to say what is going on. If your work unit is continuing to progress, then let it run. If it is stopped, then try to start it again with another reboot. Lawrence |
||
|
|
dondee
Advanced Cruncher Joined: Jan 16, 2006 Post Count: 100 Status: Offline Project Badges:
|
Thanks for answering Lawrence, I rebooted then shut down and cold booted but there is no change so I have suspended the wu for now.
The run times have changed before when rebooting/booting the computer, but not this drastic also, the "to completion" time was not affected. Maybe this is just a fluke and I will probably abort this wu later. Do aborted wu become available for some one else to process? Thanks |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Hi,
----------------------------------------What client version are you running? If 6.6, you may see very warped times since they are based off wallclock. I've had on resumes silly situations such as 7 hours CPU time, 1 hour wallclock after restart. With 6.6 click the result in the task window and hit the properties button on left. See FAQ for more. On restart there is loss because the result resumes from the last good checkpoint that was saved. When computers crash at the wrong time, that loss can be larger. Yes all results will be redistributed until a validation is possible or the distributor has determined that the result is bad (after 7 errors).
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
nly32630
Advanced Cruncher The Netherlands Joined: Dec 3, 2007 Post Count: 138 Status: Offline Project Badges: 
|
Hi, What client version are you running? If 6.6, you may see very warped times since they are based off wallclock. I've had on resumes silly situations such as 7 hours CPU time, 1 hour wallclock after restart. With 6.6 click the result in the task window and hit the properties button on left. See FAQ for more. Maybe it helps to run CPU benchmarks? Switch to Grid or Advanced view, click on Advanced (pull down menu) then on Run CPU benchmarks. It takes a minute, work will be suspended for a while, then the estimated time might change I have seen the estimated times change after doing this, at one of my devices. After a reboot the estimated time was changed, so I tried this.
Greetings,
Arjan  |
||
|
|
dondee
Advanced Cruncher Joined: Jan 16, 2006 Post Count: 100 Status: Offline Project Badges:
|
Sekerob,
I am using 6.47 on this machine. |
||
|
|
dondee
Advanced Cruncher Joined: Jan 16, 2006 Post Count: 100 Status: Offline Project Badges:
|
nly32630,
I ran the cpu benchmarks, no change, then rebooted and ran again. Still no change. It is strange that it only affected one and not all of the running wu. |
||
|
|
4WhQxmsSdepBpEBjB6rbNUMSgTfK
Veteran Cruncher The Great State of Texas Joined: Apr 27, 2007 Post Count: 1053 Status: Offline Project Badges: 
|
Not much help but...
----------------------------------------I've noticed more than once the completion time is way off.. It will say 1-2 hrs left when the work unit finishes (w/o error I might add). I think of it more as a est. and not a act. time.  |
||
|
|
dondee
Advanced Cruncher Joined: Jan 16, 2006 Post Count: 100 Status: Offline Project Badges:
|
PecosRiverM
I often see differences in the estimated time and the actual completed time, but never have I seen a change of 18 hrs of the estimated time. All the rest of the wu are still at 6:45, give or take. I think I will abort this wu, I don't want to put 24 or more hours in it and have it error out. Thanks for all the ideas but I guess this is one of those "who knows". |
||
|
|
dondee
Advanced Cruncher Joined: Jan 16, 2006 Post Count: 100 Status: Offline Project Badges:
|
I did not abort this wu and it finished in a total of about 14 hours, that a little sooner than what the 25 + hours that was indicated. I have seen many of these wu change in completion time but never one this far off.
|
||
|
|
|