Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 3
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1500 times and has 2 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Priorities

It would help if your software would prioritize the tasks by their deadlines.
[Jul 12, 2012 11:40:44 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Coleslaw
Veteran Cruncher
USA
Joined: Mar 29, 2007
Post Count: 1343
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Priorities

curious2012, this is a BOINC programming issue and should be suggested with the Berkeley crew. http://boinc.berkeley.edu/dev/forum_forum.php?id=2
----------------------------------------

[Jul 13, 2012 12:27:03 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Priorities

Not going to happen. The design is not just for WCG, it's a x-project scheduling rule to process on the basis of FIFO, first in, first out. Only when there is threat of overrunning the deadline [not completing in time], will there be prioritization on basis of Earliest Deadline First [EDF]. This is automatic, no user management required.

edit: It used to be possible with certain clients to use the "Switch application every..." to some inflated number such as 6000 minutes, to auto-force the short deadline tasks ahead in the queue [those that have an original deadline of 4 days for instance]. Those running with large buffers that cause tasks not to make deadline have created their own problem. Reduce the additional buffer / connect about every sum total to less than the shortest deadline i.e. if the shortest deadline of any work your client receives is 4 days, set the sum total of connect/additional buffer to e.g. 1.00 + 2.00 days. Then all tasks make it easily. If your machine is part time computing, on an irregular schedule [dont know when on and for how long], reduce the connect/additional buffer to zero. This way the client only has tasks that are being run immediately upon receipt. In a nutshell.

Without explaining why this is wanted or needed [e.g. scenarios], there cant be a direction on how to best customize the client settings of web preferences.
----------------------------------------
[Edit 2 times, last edit by Former Member at Jul 13, 2012 6:22:59 AM]
[Jul 13, 2012 6:10:34 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread