[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
re: [Condor-users] about scheduling algorithm in condor and condor-g
- Date: Wed, 9 Feb 2005 18:14:11 +0800 (HKT)
- From: "Carson Hung" <carson@xxxxxxxxxxxxxx>
- Subject: re: [Condor-users] about scheduling algorithm in condor and condor-g
First of all, thanks for your reply.
we are going to test a new scheduling algorithm in condor/condor-g, so we
would like to know if it is possible to use something like plugin in order
to change the current scheduling algorithm other than using classad.
> "Carson Hung" <carson@xxxxxxxxxxxxxx> wrote:
>>I am new to condor and condor-g.
>>I think that both condor and condor-g are scheduler for the jobs in the
>> queue. However, May I ask a question on the scheduling algorithm used
>> by condor and condor-g, are they using FIFO?
> only the mpi universe is fifo. For all job types other than mpi, condor
> uses a priority queue instead of fifo. The priority sort is first cut
> by the submitting users priority, then by the job priorty, then by
> submission time. So with condor, if the user 'ahead' of you in the
> queue has 1000 jobs submitted, no worries, it doesn't matter because
> when your jobs run are not impacted by how many jobs other users have
> submitted (unless you all submitted mpi jobs, since mpi is indeed
> treated fifo for now).
> can I change the scheduling
>>algorithm in it?
> you can change the scheduling behavior big time by using job and machine
> classad expressions. Also you can control preemption settings. Also
> both user (condor_usrprio) and job (condor_prio) priorities. ClassAds
> makes setting up scheduling policy very different from other (more
> traditional?) systems, but it is very flexible, esp in a distributively
> owned setting.
>>Condor-users mailing list
> Condor-users mailing list