[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Filling pool breadth-first with partitionable slots (Beyer, Christoph)
- Date: Mon, 31 Oct 2016 16:09:07 +0000
- From: Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>
- Subject: Re: [HTCondor-users] Filling pool breadth-first with partitionable slots (Beyer, Christoph)
I whipped this up a couple of years ago:
STARTD_ATTRS = $(STARTD_ATTRS) DynamicSlotID
DynamicSlotID = ifThenElse(DynamicSlot, regexps("slot\d+_(\d+).*", Name, "\1", "i"), UNDEFINED)
However I don't think this will help much with ranking.
There's also a NumDynamicSlots attribute which may be what you're looking for - you'd rank the partitionable slots with the lowest number of dynamic slots highest. I'm not sure which version that attribute appeared in, though.
Personally, I prefer depth-first fill because the Linux buffer cache coupled with a 12-hour automount timeout helps limit the amount of NFS traffic generated by jobs starting up, as most of our jobs pull inputs from NFS filesystems rather than an input transfer.
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Jason Liu
Sent: Monday, October 31, 2016 3:39 AM
Subject: Re: [HTCondor-users] Filling pool breadth-first with partitionable slots (Beyer, Christoph)
Thank you for your email.
While the solution you suggested works for static slots, it doesnât work for p-slots. SlotID is always 1 for p-slots since p-slot names are slot1_1, slot1_2 etc instead of slot1, slot2.
Unless I am missing something?