[HTCondor-users] Filling pool breadth-first with partitionable slots

[Jason Liu <jason.liu@xxxxxxxxxxxxx>]

Hi,

We have a need to fill our HTCondor pool breadth-first to improve IO efficiency.

We are using p-slots in our pool, since our jobs come in all sorts of shapes and sizes.

I am a bit lost as to how to configure a pool to fill breadth-first. By default it seems HTCondor fills depth-first. 

After some research, I have found this article:

https://htcondor-wiki.cs.wisc.edu/index.cgi/wiki?p=HowToFillPoolBreadthFirst

which shows a way to fill the pool breadth-first. However the solution presented has one major drawback for p-slots, which is that each machine can only match one new job per negotiation cycle. 

We are looking for a way to fill our pool breadth first, without the limitation of only being able to match one job per negotiation cycle per machine. Does HTCondor have a way to overcome this?

We are using HTCondor 8.4.7. In addition, we are also using concurrency limits and consumption policy is enabled on all machines in the pool. 

Any help would be greatly appreciated.

Thanks.

Kind Regards,

Jason

PRIVACY AND CONFIDENTIALITY NOTICE
The information contained in this message is intended for the named recipients only. It may contain confidential information and if you are not the intended recipient, you must not copy, distribute or take any action in reliance on it. If you have received this message in error please destroy it and reply to the sender immediately or contact us at the above telephone number.
VIRUS DISCLAIMER
While we take every precaution against presence of computer viruses on our system, we accept no responsibility for loss or damage arising from the transmission of viruses to e-mail recipients.