| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Stop TB
Thread: Increased duration of task |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Template
Cruncher Joined: Oct 31, 2008 Post Count: 20 Status: Offline Project Badges: 
|
Hi I see regularly with HSTB jobs that they start out planned to take up to 9 hrs or so, however they turn out up to double that time or even more with this one:
----------------------------------------HST1_010728_000092_AC0004_T325_F00094_S00015_0 Elapsed 1d 07:06.. remaining 1d 12:53... How can this take up so much more time and will it still result in correct calculation or is an error responsible for this 6 fold in time? Update: it is now still running for another 1d20:33... It is apparantly not going anywhere as it is stuck at 45.752%. So I guess I need to cancel this job. Too bad, it was running for so long already... Gerben [Edit 2 times, last edit by Template at May 27, 2017 9:41:34 PM] |
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1326 Status: Offline Project Badges: 
|
In the case of a task the best thing to do is restart your computer. Once restart is complete your task should start from last saved checkpoint.
----------------------------------------You can check when the last checkpoint was made by clicking on the task name then click properties look for a CPU time at last checkpoint then they have a look at CPU time. And that the event there is a massive difference depending on how often you have checkpointing set in your preferences if there is a massive difference say an hour you know the task is possibly stuck.  |
||
|
|
Template
Cruncher Joined: Oct 31, 2008 Post Count: 20 Status: Offline Project Badges:
|
Hi Speedy51, thanks. I will keep that in mind for the next time... :)
|
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1326 Status: Offline Project Badges:
|
Hi Speedy51, thanks. I will keep that in mind for the next time... :) Happy to be of assistance |
||
|
|
retsof
Former Community Advisor USA Joined: Jul 31, 2005 Post Count: 6824 Status: Offline Project Badges: 
|
In the case of a task the best thing to do is restart your computer. Once restart is complete your task should start from last saved checkpoint. You can check when the last checkpoint was made by clicking on the task name then click properties look for a CPU time at last checkpoint then they have a look at CPU time. And that the event there is a massive difference depending on how often you have checkpointing set in your preferences if there is a massive difference say an hour you know the task is possibly stuck. Mine wasn't stuck. It was running, but not getting many cycles. The remaining time was also increasing. This solution did work for one of mine after I saw your message. There is a weirdball solution to this. I had one that had run 79 hours on a 50% power laptop with 19 hours remaining that was still going up. Exit BOINC and REBOOT. Mine now shows 8 hours completed with 9 hours remaining.
SUPPORT ADVISOR
Work+GPU i7 8700 12threads School i7 4770 8threads Default+GPU Ryzen 7 3700X 16threads Ryzen 7 3800X 16 threads Ryzen 9 3900X 24threads Home i7 3540M 4threads50% |
||
|
|
Template
Cruncher Joined: Oct 31, 2008 Post Count: 20 Status: Offline Project Badges:
|
Hi Speedy. Thanks for the reply. Indeed that would help. I simply restart the BOINC client now. Works also...
Happy Crunchin' |
||
|
|
|