| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Stop TB
Thread: Unusually Long Computation Time |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have a workunit that's been running for 1 day 3 hours and is only about 18% done. The estimate remaining is about 5 days 4 hours! The longest for this project on this machine is 22 hours (windows 10, i5 2.5GHz cpu running 4 threads). I notice that this jobs cpu usage is only 1% and although it is an x86_64 project it is running as 32 bit according to task manager. There are also 3 fahb 32 bit jobs running but everything seems okay with them. I notice a previous user had an error status with this hst1 workunit. I'm considering aborting it. Any thoughts?
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If you haven't yet, you might try shutting down and doing a cold boot.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes, rebooting proved to be a better solution. The CPU usage is now normal but it shaved the runtime down to 4 hours with 5 hours projected remaining. Good enough. Thanks for the suggestion.
|
||
|
|
Seoulpowergrid
Veteran Cruncher Joined: Apr 12, 2013 Post Count: 823 Status: Offline Project Badges: 
|
Glad the reboot worked for you. I just had that happen yesterday. It was at 47% with 1 day of running time. Nine hours later the percentage didn't change at all. A reboot brought down the run time to 6 hours but it later finished and is Pending Verification.
---------------------------------------- |
||
|
|
retsof
Former Community Advisor USA Joined: Jul 31, 2005 Post Count: 6824 Status: Offline Project Badges: 
|
Glad the reboot worked for you. I just had that happen yesterday. It was at 47% with 1 day of running time. Nine hours later the percentage didn't change at all. A reboot brought down the run time to 6 hours but it later finished and is Pending Verification. I don't know why, but the rebooting did help and apparently forced a recalculation. One happens to be running on a laptop at 50% power (twice as long to keep the heat down). It was running away with apparently few CPU cycles used showing 79 hours completed with 19 hours remaining. The remaining hours were slowly increasing, so that was why I was watching it. I exited BOINC to get a normal exit, rebooted, and it now shows 8 hours completed with 9 hours left. This one is due on July 23, so it should finish.
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% [Edit 1 times, last edit by retsof at Jul 21, 2019 2:53:12 PM] |
||
|
|
retsof
Former Community Advisor USA Joined: Jul 31, 2005 Post Count: 6824 Status: Offline Project Badges:
|
If you haven't yet, you might try shutting down and doing a cold boot. It worked for me. The runaway with 79 hours done and 19 hours remaining now shows 8 hours completed and 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% [Edit 1 times, last edit by retsof at Jul 21, 2019 3:09:43 PM] |
||
|
|
|