| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: start order for Wu's |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'm usine Boinc, version 6.10.58 and I have in cache a lot of small work units for the Csfw project.
Boins doies not start th work units accoridn to their arrival order, nor does it according to their date limit for being sent. It start the units apparently randomly, starting recently downloaded units which have a lot of time to be sent, and forgets old units, downloaded since a big amount of time. I miight as well be too late to sent these units back. Is there a parameter to force boinc to start units according to their limit date for being sent and starting the unit which have the less time available ? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have the same version of Boinc and 4 days CFSW WU in cache. On 8 thread procesor it's a lot of WU. But I can see, that sometimes Boinc automaticly suspends WU with long validation date, and starts WU with short validation date (even there is nearle 4 days of time left for them). Actually it's going pretty often. So, as I can see, Boinc is doing good job to return all WU in time.
|
||
|
|
jasm580
Senior Cruncher USA Joined: Dec 20, 2007 Post Count: 157 Status: Offline Project Badges: 
|
I am glald someone posted this. I have been seeing this for a couple of weeks now. As soon as it needs to kick into high priority mode it wants to favor some of the more recent w/o and let the ones that will soon expire just sit. Using Version 6.10.58
----------------------------------------
-Jasm
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Once the scheduler algorithm gets worried and stops using the default 'in order' sequence, things get very strange as it runs work units for short periods to see how fast they are and eventually picks some for steady running.
 This has always bothered people, which is why the algorithm is always being changed. I stopped trying to figure it out less than a year after I started using BOINC.Lawrence |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7849 Status: Offline Project Badges: 
|
If you really want to micromanage your queue you can suspend all of the WU you do not want to run and then BOINC will start the ones you want to have finished. Be aware however, that if you have suspended any WU, BOINC will not auto fetch any new ones and you may have to force it to report finished ones.
----------------------------------------Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
or lower cache below 10 days so that a wu that takes slightly longer to complete does not kick the dcf over 10 days
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My BOINC_v7.0.27 and 7.0.28 ones do not seem to have a lower-limit when to trigger its so-called 'panic-mode'. I had a WU running (normally) under BOINC and then BOINC suspended that WU to run an earlier-deadlined WU under high-priority. Guess how much time-left BOINC indicated that the suspended-WU had remaining? Seven(7) seconds! I had to manually intervene to let the suspended-WU run the seven(7) seconds and that WU did successfully complete after the said seven(7) seconds. Having a somewhat more-than-adequate RAM amount in my machines made the said manual intervention as something that is not critical from a stability/performance point-of-view.
----------------------------------------; ; edit1_2012.09.20Th.0757.utc: ; -- typo/grammar check ; [Edit 1 times, last edit by Former Member at Sep 20, 2012 7:57:06 AM] |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
I'm usine Boinc, version 6.10.58 v6.10.xx is probably the most buggy clients as far as deadline-scheduling goes. Is there a parameter to force boinc to start units according to their limit date for being sent and starting the unit which have the less time available ? Forcing earliest-deadline-first (EDF)-mode is easy, just increase your "Connected..." and if any task has "time-to-deadline" < "Connected..." it will run in EDF-mode... ... Well, except, v6.10.xx will happily crunch tasks for a BOINC-project with over 1+ month to their deadline, while tasks in another BOINC-project will not be crunched, even after their deadline has passed... For WCG-only users you shouldn't be affected with this particular bug.  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This preempting to included [near 100% complete] has been frequently discussed at developers and it will *not* be addressed! The task will finish on it's next round robin turn or when the FIFO order resumes.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This preempting to included [near 100% complete] has been frequently discussed at developers and it will *not* be addressed! The task will finish on it's next round robin turn or when the FIFO order resumes. The nature of deadlines can not but be time-based, not FIFO based. Because the idea of a deadline takes the back seat to the idea of a FIFO under BOINC as you hinted, why not suggest to those developers to do away with having deadlines for WUs? Why not use serial-numbers then if FIFO is the right way to do 'deadlines'?; |
||
|
|
|