| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Way to compute by earliest due? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I've noticed that BOINC for Windows has an odd way of picking which task to compute next. I am not, however, quite able to determine what order it is using.
I have determined it is NOT using the most sensible method of 'Earliest Due-By Date', which would help a computer not go overdue on assignments. Is there any way to modify this, so that I don't timeout on assignments simply because BOINC didn't decide to get around to that one, even though it was doing ones due 2 or 3 days later? |
||
|
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4894 Status: Offline Project Badges: 
|
PhoCoe, welcome to the forums.
Have you had workunits go "overdue on assignments"? If so, your cache is too large. Boinc will sort things out in its own way, and there is no way to modify this. If you have workunits that do not complete before they are due, then lower your cache setting and see if that helps. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes, I have had workunits go overdue. My cache is not all that large, actually, and due to a lack of continuous WiFi, I can't really shrink it and keep the computer working all the time.
If there's no way to change this, there's no way to change this. A shame, that, and I think this ought to be fixed. Who do I contact about the Boinc client? From a programmer's standpoint, 'sorting things out in it's own way' is illogical. Sorting them by deadline is... the only way that makes sense. A slightly larger cache wouldn't hurt then, as it would go through the assignments due first, thus opening up more room in the cache for things that would then be due later than anything currently downloaded... etcetera. If you see another logical way to sort things, or can explain how the way it is currently sorting things IS logical, please explain. Who takes care of client bugs, issues, and feature-requests? Where would I go to get in contact with them? |
||
|
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4894 Status: Offline Project Badges:
|
From a programmer's standpoint, 'sorting things out in it's own way' is illogical. Sorting them by deadline is... the only way that makes sense. A slightly larger cache wouldn't hurt then, as it would go through the assignments due first, thus opening up more room in the cache for things that would then be due later than anything currently downloaded... etcetera. If you see another logical way to sort things, or can explain how the way it is currently sorting things IS logical, please explain. Who takes care of client bugs, issues, and feature-requests? Where would I go to get in contact with them? If you think this is a bug then you need to go to the Boinc developers forum to complain: https://boinc.berkeley.edu/dev/ |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The way the client schedules tasks is first order in FIFO -by attached project-, for very good reasons. Only if task(s) will not make it waiting their turn, will they be put ahead. Base outline:
https://boinc.berkeley.edu/trac/wiki/ClientSched |
||
|
|
|