Re: [HTCondor-users] lower latency scheduling

[Cole Bollig <cabollig@xxxxxxxx>]

Hi Rita,

Once a Schedd has a claim on Startd resources for a user the Schedd will try to run as many jobs that it can on those resources up to CLAIM_WORKLIFE seconds. Increasing the CLAIM_WORKLIFE would cause those claims to stay alive longer and get user jobs running once the resources are available again.

If you truly want to just increase the amount of negotiation cycles in the hopes of making more matches to resources, then you could try reducing the SCHEDD_INTERVAL and NEGOTIATOR_INERVAL.

-Cole Bollig

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Rita <rmorgan466@xxxxxxxxx>
Sent: Thursday, May 25, 2023 5:29 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] lower latency scheduling

 

I am trying to think of ways to lower my scheduling latency. My machines on Azure are relatively powerful. 256 cores, 2TB of memory, fast NVME local disks.  I have 30 of them in my HTcondor pool. 

My job profile is: they are small running jobs. each take like 30s to 5 mins to run. When the user submits the job, I want the scheduler/negotiator to aggressively match. No preemption. What are  some knobs we can tune for a setup like this? 

--

--- Get your facts first, then you can distort them as you please.--