Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Condor on SMP machines
- Date: Wed, 20 Jun 2007 15:26:34 -0500
- From: Alan De Smet <adesmet@xxxxxxxxxxx>
- Subject: Re: [Condor-users] Condor on SMP machines
Urs Fitze <fitze@xxxxxxxxxxxx> wrote:
> A, B, C: 100% each -> 1 CPU per job
> E and F: 50 % each -> 2 jobs on 1 CPU
I'm a bit surprised by this, but this is really a OS level
scheduling decision, not one by Condor.
Condor can make fairly intelligent scheduling decisions, you just
need to define things in a concrete way that Condor can work
with. What does a "direct-job" mean? You mean a user logged in
and ran something on the command line? Does that mean any
process, even "less README"?
If you can name down your definitions in the form of a script,
you can use Condor's cron-like functionality to add additional
attributes to your startd ClassAds. You can then modify your
policy (SUSPEND, CONTINUE, PREEMPT, KILL, and friends) to use
this information. So if you have a script that reports things
like NUM_DIRECT_USER_JOBS=3, you can have a PREEMPT expression
that includes something like "((4 - SlotID) <
NUM_DIRECT_USER_JOBS)"
Condor's cron-like functionality:
http://www.cs.wisc.edu/condor/manual/v6.9/3_3Configuration.html#param:NumSlots
(Note, where I said, "slot" above, the terminology is "VM" in
Condor 6.9.2 and earlier.)
--
Alan De Smet Condor Project Research
adesmet@xxxxxxxxxxx http://www.condorproject.org/