| 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: 6
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello all,
I tried for some minutes to find an answer to my question in the topic using the search forum, but I did not succeed. I would like to know if there is a possibility to rearrange all downloaded task in that way that the task with the shortest return time will be executed first. At the moment all tasks are executed in that way I download them. If I missed some thread where it was discussed before then pls post the link to it. If this is not possible up to now, it could be an improvement best regards Bravehart |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
AFAIK there is no way to change the execution order unless you manually micro-manage tasks by suspending and resuming each and every work unit.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello Bravehart,
There are some tricky scheduling differences between different versions of BOINC, but the short answer is that there is no simple way to do this. You can Suspend tasks you do not wish to run, but then you are trapped into constant manual control.Lawrence |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Wow it took only ten minutes to get two answers to my question. You both are very fast :)
----------------------------------------I thought in that way because I could not find any option in my BOINC client. Actually I do not have any problems receiving tasks with shorter return time, but it would be good to have some savety time by executing the task with the shortest return time first. I guess this is a boinc topic and I should raise this topic in their forum ? [Edit 1 times, last edit by Former Member at Apr 16, 2010 9:00:10 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
one thing I do is to suspend everything but that task until it gets about 10 min time logged (1-2% usually) resume all tasks, suspend new task, then resume it. this gets it running in order recieved again, but changes status of repair job to "Waiting to run" instead of "Ready to Start" as jobs complete WTR jobs are started first in order recieved, then RTS jobs. Once all WTR jobs are running it goes back to next recieved order.
|
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Gents,
----------------------------------------principally there is no need whatsoever to manually intervene in the normal FIFO processing order. Rather often than not it causes more issues than it resolves. Only when you know that a task will take longer than to the deadline i.e. TTC is completely underestimated should such stop start suspend action be undertaken. The adage is though a smallish cache like 1 day, then a long DDDT2 A-Type task gets always started within 24 hours and gets completed within the next 7 days, that is unless the device is really really slow. Generally if WCG notices a device is slow it will even automatically increase the deadline up to 2x normal, but as said unless these are known monster jobs that have wrong completion time predictions, there's no need to MM. cheers
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|