Message boards : Server programs : Run tasks by earliest deadline
Message board moderation
Author | Message |
---|---|
Send message Joined: 31 Jul 18 Posts: 1 |
Is it possible to accept tasks but automatically suspend old tasks in place of newly added tasks that have much earlier deadlines? |
Send message Joined: 19 Nov 16 Posts: 63 |
On the client? |
Send message Joined: 25 May 09 Posts: 1295 |
This is a client-side function that already exists (well, so of). The client normally runs in First-in, First-out mode If a task is detected by the client as probably not going to complete in time if it runs in sequence the it is promoted to run early, thus (hopefully) complete in time. This has to be a client-side function because the client knows what work it has in hand, but the individual project servers only know about the work they have sent out. |
Send message Joined: 5 Oct 06 Posts: 5121 |
I found the original question ambiguous. It could be a client-side question, but it's unusual for someone to go right down to the bottom of the list and pick the server area for those. He could just as easily have been referring to Prioritizing jobs in a multi-user project. That's server documentation, and the 'users' in this case are the research scientists. In server land, the task deadline is known as the 'delay_bound', and is set in the input template. I don't know enough about user accounts and input templates to comment about how the delay bound and the job priority could be made to interact dynamically. |
Send message Joined: 19 Nov 16 Posts: 63 |
Theres some flags that you can work with for the feeder here: https://boinc.berkeley.edu/trac/wiki/BackendPrograms |
Send message Joined: 18 Jul 18 Posts: 4 |
Is there a setting somewhere that can change the 'first in/first out' operation of the client? I frequently find myself suspending tasks more recently downloaded in order to make sure older tasks complete successfully on time. D Lambert Chemainus, BC Canada |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.