Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 12
Posts: 12   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1523 times and has 11 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Clean decommisioning

The general idea seem to be user-control of WU-execution. At the highest level, the WUs are crunched before the WUs' deadline; how it was crunched should be placed under user-control. BOINC needs to devolve some aspects of the WU-execution control to the user. The app_config in BOINC_v7.0.42 is a step in that direction. I expect further refinements there like timing controls of start (or interrupt) of execution of WUs and their sequence of execution.

How about the "No new tasks" button, Jim1348? KISS enough for me and this one in version 7 client even takes to reporting all completed tasks immediately. Those in a rush could abort any non-started tasks too.
I use that too, but if you are running CEP2 and need to reboot as soon as possible without losing work, then you really need to be able to stop at the end of the current work unit.
If only we have an ACBI (auto-checkpoint before-any-interruption) feature and the WUs are coded to be able to do that, then there would have been no issue when and what WUs to interrupt at any time and/or for any reason.
;
; andzgridPost#796
;
----------------------------------------
[Edit 1 times, last edit by Former Member at Jan 8, 2013 9:18:16 PM]
[Jan 8, 2013 8:11:29 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Clean decommisioning

To enroll as tester / idea inserter go http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha (posted this link for you before) and explain the problem and solution. Maybe amstrdj, knreed, uplinger, seippel and cleanenergy never discussed the case ** to include with Berkeley and failed to consider the pros and cons [e.g. user impact when 8 concurrent get saved at 8-16GB per interruption and reload]. Somehow the one big con could and will outweigh the wishes of the micro-manager all too over-concerned of a few hours progress reversal [notwithstanding the special notification sheet of why things are what they are].

P.S. The techs also explained in the case of another science, what is needed done at point of resume by the applications to ensure that a task remains integer. May not apply to all sciences [sizing up asteroids springs to mind], but I'd like to think that if we compute a compound docking, that all bits are pointing proper on resume and not one being off, the difference between a cure and a cancer.

** Actually they did, several times and surely more often then I know off.
----------------------------------------
[Edit 1 times, last edit by Former Member at Jan 9, 2013 2:25:03 PM]
[Jan 9, 2013 2:23:29 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 12   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread