Hello, This Feature Request is a bit confusing to me. I think I get it, but I am not sure. I will present what I think you mean, and if it is the case, would you re-write the Feature Request using my terminology and resubmit it? Also, please clarify the the first part of your example (current system with one priority) by showing the priorities and fictive start and stop wall clock times for each job, and add to the second part of your example by showing the two priorities for each job and fictive wall clock times when each job starts and stops under the proposed two priority system.
As I see it, you are asking to implement a "Client Priority = nn" directive in addition to the current Priority. The current Priority will be applied to jobs as it currently is, then in addition if two Jobs from the same Client have the same Priority but different Client Priority, the job with the higher Client priority (lower number) will run first. On Tuesday 10 April 2007 21:29, Darien Hager wrote: > Item 1: Allow per-client job priority ordering > Origin: Darien Hager <[EMAIL PROTECTED]> > Date: Date submitted (e.g. 28 October 2005) > Status: Initial Request > > What: > > Allow an optional per-client priority setting which is applied AFTER > the current priority scheduling algorithm. > > Applies only within the group of waiting jobs (ergo with the same > global priority) that are also associated with the same Client. The > higher priority (lower priority number) job will always be run first. > Applying it only after the global priorities should make > implementation easier. > > Why: Like the current global priority, allows ordering of jobs > to be preserved for clients. Unlike the current system, allows other > clients to proceed independently of one another so that a single > client will not hold up others. > > Notes: > > Example: > > Two clients (1 and 2), with two jobs per client, referred to as job > types A and B. Under the current system, you can set A's at priority > 10 and B's at priority 11, and have A scheduled to run 10 minutes > before B. This completes the given requirement that A should always > precede B on either client, perhaps because they have a run-script > dependency or significant relative importance. > > Let's call the client/job combinations 1A, 1B, 2A, 2B, and assume > that due to differences between the clients, the times taken for each > job vary, perhaps one client has more of one kind of files than the > other does, etc. Job times required: > > 1A: 30 minutes > 1B: 10 Minutes > 2A: 10 minutes > 2B: 30 minutes > > Under the current system, all clients will be done in 60 minutes, > since all A jobs are one block, and all B jobs are a separate block, > and each block must take as long as it's longest job. > > With per-client priorities (and all four jobs under the same global > priority level) all clients complete within half the time at 30 > minutes, due to removing unnecessary idle time. > > > -- > --Darien A. Hager > [EMAIL PROTECTED] > > > > ------------------------------------------------------------------------ > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV__________________________________ > _____________ > Bacula-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/bacula-users > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-users
