| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Boinc restarts tasks from 0 after they have processed time |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
jolufe50
Cruncher Joined: Dec 26, 2005 Post Count: 2 Status: Offline Project Badges: 
|
Hi folks
I have noticed that some task restarts from 0 after they have a long % of process, this happens to me when I exit Boinc and turn off the laptop, next day when restart Boinc, task start over again losing all the % it alredy had, this have happened to me several times, and it's a waste of time, what can be the cause of this problem ?. Thanks in advance |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi,
What science is this? Normally when doing and orderly powerdown the tasks are supposed to resume from the last checkpoint that was saved. For some systems the shutdown is too fast, so BOINC does not have the time to properly close. This was an issue that first appeared with Windows Vista [with a delay function to correct the problem - In FAQs -] "A" way around this problem is to use "hibernation" instead of power/shutdown. Then the memory state is written to disk and loaded again when you power on. Not even a second of computing lost. I've tested this through Window 8, Pro. Works great for me. |
||
|
|
jolufe50
Cruncher Joined: Dec 26, 2005 Post Count: 2 Status: Offline Project Badges:
|
Hi
Thanks for your reply, what you suggest sounds a good workaround (I try also pause the task and restart next day, sometimes works, sometimes do not), I will try that, but another "funny" thing is that sometimes when I restart the task, initially the time and % looks like it was at time of shutting down the system, but then after a few minutes, resets to 0, also lately I'm getting a message like "computation is too high" or something like that and the same thing happens, the task resets to 0, maybe something is wrong on my side. Thank you  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
"Suspending - Computation is to high" is because you or some process is taking too much processor time [default >= 25%] **, so BOINC stops. You still have not told us which science(s) this is happening on, but on the website device profile or local preferences you can choose "Leave application in memory when suspended". Tasks remain in memory when the client is paused for whatever reason (not suggested for computers that have only 512mb RAM and no decent swapfile / virtual memory size).
----------------------------------------Time only going back a little after start-up is, because the client is not immediately updating the screen. Not sure, but it could be the client is also trying to see if the task can be properly restored, and if not, it goes back to the last good saved point... which could be at the beginning. Considering some sciences need 15-20 minutes on a semi-fast computer to even reach first checkpoint, you stopping the computer [not sleep/standby or hibernate], means the computing time is surely lost. ** Many test and find that they can switch this function off [set to zero], or set it much higher without ever noticing that. WCG recommends 50%, but even 75% is save for most everyone that uses the computer intensely. [Edit 1 times, last edit by Former Member at Dec 3, 2012 5:25:26 PM] |
||
|
|
|