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 |
Hi,
----------------------------------------We've got a process that has been running for 33+ hours (4+ CPU hours) but is stalled at 82.222% progress. This task usually takes about 4 hours to complete. Suspend/resume do not seem to get the process going again. All other processes on this machine are running fine. What is the best practice with stalled processes? Do we abort the process or is there a way to recover the work done so far. Regards [Edit 1 times, last edit by Former Member at Jan 18, 2012 7:27:37 AM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi and welcome to the forums.
----------------------------------------You are very likely using a client that is not allowed to run 100% of CPU time, when on. Best practice, for DSFL and GFAM who are known to not like the repeated stop restart that throttled BOINC CPU time causes [at 60% default running 3 seconds, pausing 2], is to set CPU time to 100% or switch in the Activity menu option to Run Always. Suspend/Resume only works if the preferences are not set to unload a paused/stopped task [Leave application in memory, when suspended]. This option has to be off [temporarily if normally running with LAIM]. When stuck, simply restart the client [proper exit via the BOINC Manager exit option or stopping the service via Task Manager]. The job will restart and continue or crash [which otherwise would have been anyhow when aborting them]. This restarting a client is of course the rude way, as all jobs running will be restarted with loss of progress since last checkpoint --//-- [Edit 1 times, last edit by Former Member at Jan 18, 2012 7:43:04 AM] |
||
|
|
![]() |