[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] GPU-optional matching?

Hi Michael,

Interesting situation.

Iâm wondering if Brian Bockelman and CMSâs htcondor week presentation on resizable jobs could apply here.

Seeing as the RequestGPUs syntax is so similar to RequestCpus.


Itâd prefer to run with a GPU but doesnât have to.

Cheers, Iain

On Jun 13, 2016, at 17:51, Michael V Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx> wrote:

So we've got a situation where certain jobs can run better if a GPU is available, but can still run fine without one. This poses an interesting problem - the "request_gpus" line bakes that request into the job requirements _expression_, so that the job won't run unless it can get a GPU for itself.

Is there any clever trick anyone can think of which will reserve a GPU and set up the appropriate environment variables if one is available, but still allow the job to match and run even if it can't? I think my difficulty is that I'm not quite clear on how a request for a resource becomes a deduction from the pool of that resource on the machine - I think it comes down to needing the deduction to take place when it matches even if it's not mandatory for the job.

        -Michael Pelletier.
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at:

Attachment: smime.p7s
Description: S/MIME cryptographic signature