| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 48
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Rather thin on the ground in expertise if this sekerob is needed. Searching on this member and a few key words pops up this post though: http://www.worldcommunitygrid.org/forums/wcg/viewpostinthread?post=440196 . Looks like any task that has a remaining deadline of less than two times the actual buffer causes such a task to skip ahead.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks to everyone who tried to help. I'm rather thinking I should have stayed with the old level ...
Some of Rob's posts talked about WCG pholks liking to have EDF (earliest deadline first), but that's clearly not something that the BOINC developers want to do nor is it something that the WCG techs felt the need to push for. Oh well, c'est la guerre. |
||
|
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4894 Status: Offline Project Badges:
|
Boinc 6.10.58 often did not start resend workunits soon enough and would go into crisis mode trying to get them done by starting and stopping partially completed workunits in a seemingly ad hoc manner. To prevent this from happening we went to great lengths to start resends as soon as possible. One major improvement in the newer versions of Boinc is that it is much more intelligent in how it schedules workunits. It rarely (if ever) goes into crisis mode, and resends eventually get crunched without pausing partially completed workunits. There really is no reason anymore to try to get resends started immediately.
|
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges:
|
I confirm that the "Switch between applications every..." parameter that I have highlighted in August 2009 as triggering High Priority mode for repair WUs stopped to have this side effect with versions 7 of BOINC.
----------------------------------------However I can also confirm that WUs with shorter deadlines are raised to high priority sooner or later in my machine although it is running with a 1+0.2-day queue and thus repair WUs have almost no chance of being reported late. And thinking of it, if like me you like to micromanage occasionally that leaves you a chance to have some tasks to push ahead. ![]() |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7848 Status: Offline Project Badges:
|
Boinc 6.10.58 often did not start resend workunits soon enough and would go into crisis mode trying to get them done by starting and stopping partially completed workunits in a seemingly ad hoc manner. To prevent this from happening we went to great lengths to start resends as soon as possible. One major improvement in the newer versions of Boinc is that it is much more intelligent in how it schedules workunits. It rarely (if ever) goes into crisis mode, and resends eventually get crunched without pausing partially completed workunits. There really is no reason anymore to try to get resends started immediately. Well said. The only time I have seen BOINC go into crisis mode(high priority) is when the task lengths have become highly variable on the upper end (task(s) probably 2 or more times greater than average), which throws off the initial BOINC calculations. If left to its own devices, BOINC will gradually return to a more normal mode. The ability of the program to get all existing jobs completed in a timely manner works remarkably well IMHO. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have upgraded to 7.2.47 can find little difference. The exception is that client reports finished tasks and asks for new tasks on its own, not what had happened on 7.2.27 which seemed to require me to force reporting which have up to 30 tasks waiting. So no complaints.
|
||
|
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4894 Status: Offline Project Badges:
|
I have upgraded to 7.2.47 can find little difference. The exception is that client reports finished tasks and asks for new tasks on its own, not what had happened on 7.2.27 which seemed to require me to force reporting which have up to 30 tasks waiting. So no complaints. That change was made in 7.2.36 as noted here. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Missed that posting, but thanks.
![]() |
||
|
|
|