Iâd suggest double-checking your default prio factor value â as I recall it was only raised to 1,000 in the 8.4 release, and if youâre using 8.2, it might only be 100 (if Iâm remembering correctly), and if your jobs are racking up a lot of slot time across many machines the final job may still have a higher EUP even with a priority factor of 1.
Perhaps if you specify also a dummy accounting_group_user for the end jobs, theyâd wind up in a different usage basket than the rest of the DAG and wouldnât be penalized for the large usage it incurred?
You can use condor_userprio to check on all this.
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx]
On Behalf Of Szabolcs HorvÃtth
Thanks for the tip! I tried setting up group accounting and it solved most of my problems, although it still takes more time to start the end jobs than I'd expect.
We have a negotiation cycle every 30 seconds but it takes much longer time to match slots to these jobs (around 10-15 minutes), even though there are idle slots that get matched to other jobs.
Maybe there are some claims hanging on to these slots?
On Tue, Nov 29, 2016 at 7:12 PM, Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx> wrote: