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: 1
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 320 times and has 0 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Error handling

Most errors that a WU may encounter have a high chance of being transient. (eg. Running out of resources or a spurious hardware error.) Even if the problem won't go away by itself, most may be fixed easily by the user. (eg. By adding an extra swap file or removing unneeded files from the hard disk.) However, BOINC aborts if any of those things happen and then starts another WU instead. This is about the worst, most inefficient, action possible. Is there any way to set it up so that it will simply go back to the previous checkpoint instead?

Very few of my WUs have ever aborted, but every one of them, apart from the HCC crashes, would have completed successfully if they had just been run again. It would definitely be much more efficient to be set up for retries.
[Nov 13, 2007 4:40:20 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread