Mailing List Archives
Public Access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] gpu's and preemption
- Date: Thu, 28 Feb 2019 19:54:51 -0500
- From: Michael Di Domenico <mdidomenico4@xxxxxxxxx>
- Subject: Re: [HTCondor-users] gpu's and preemption
On Thu, Feb 28, 2019 at 3:27 PM Todd L Miller <tlmiller@xxxxxxxxxxx> wrote:
> > ideally what i'd like to happen is that 4 of usera's jobs are
> > preempted for userb's. just the fact that a user is asking for a gpu
> > should be enough to preempt another person from a slot that isn't
>
> This sounds like a job for a (machine) RANK expression.
> (Something like RANK = RequestGPUs, probably.) That will work just fine
> with pslots, except ...
wait, so you're saying all i need to do is set preempt = true and rank
= requestgpus to get the desired behaviour. that doesn't sound right
the gist of what i'm trying to do is allow gpu jobs to push non-gpu
jobs off the slot and cut the line for the slot. all other jobs
should not preempt (this is where i got into trouble before). i had
huge swings in the pool as the prio's changed and jobs got preempted
given my last foray into pre-emption I'm unwilling to turn the knobs
until i know which specifically i need to turn