[HTCondor-devel] p-slots and preemption

[Brian Bockelman <bbockelm@xxxxxxxxxxx>]

Hi,

We recently tried to enable preemption on our local cluster - and, well, not much happened.

We were trying to preempt opportunistic jobs - 1.9GB RAM, 1 core requested apiece - with CMS jobs - 2.5GB RAM, 1 core.  Unfortunately, we use p-slots.  That means each opportunistic job runs in a slot which is precisely 1.9GB of RAM, too small for CMS jobs to match.

CMS jobs don't match, meaning they can't preempt, meaning the high priority folks starve in line after the low-priority folks.

I can't think of any particular way to "simply" fix this.

Thoughts?  How would this work with eje's consumption branch?

Brian

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