Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Support Forum: Suggestions / Feedback Thread: Stop intake of new Tasks but continue with the remaining Tasks computation |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 4
|
Author |
|
sken130
Cruncher Joined: Dec 5, 2014 Post Count: 1 Status: Offline Project Badges: |
Is that possible?
----------------------------------------I will have a holiday 2 weeks later, during which my computer will be shut down for consecutive 7 days. If I stop the computation just before my holiday, then some newer Tasks will be overdue. If I stop the computation right now, then no new Tasks will be in-taken or overdue, but my current Tasks will be overdue. That's the difficulty here. The Tasks will turn ugly. [Edit 1 times, last edit by sken130 at Jul 30, 2015 3:43:12 AM] |
||
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3715 Status: Offline Project Badges: |
Simply go to the Project tag in BOINC Manager and select "Don't send new work" early enough for the latest loaded tasks to have enough time to complete before you shut down.
----------------------------------------Don't forget to trigger a project update to have all completed tasks reported if necessary. ---------------------------------------- [Edit 1 times, last edit by JmBoullier at Jul 30, 2015 3:58:05 AM] |
||
|
ca05065
Senior Cruncher Joined: Dec 4, 2007 Post Count: 325 Status: Offline Project Badges: |
Another option is to set 'minimum work buffer' and 'additional work buffer' to 0 in BOINC preferences. I believe the client will then only request new work units a few minutes before it needs them. You will still need to ensure all completed tasks have been reported.
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Is a good pre-conditioning to the off-time what you propose.
There's no harm in just letting BOINC run through the end, and just before powering down before vacationing, hit project update to force reporting of any completed, abort anything running is the tasks view and hit update again to report those, then power down. This way you truly maxed to the last minutes. Any aborted task will be immediately reissued to another cruncher. Stopping work fetch 12 hours before planned shutdown and then run all to completion is of course graceful. When work fetch is stopped all results report immediately by themselves. |
||
|
|