[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] job idle and priority

On 1/18/21 7:14 AM, Beyer, Christoph wrote:

Anyway the 'job priority' is on a per-user-base and meant as a tool for users to prioritize jobs as parts of their transmision.

It does not have any effect on absolut priority between different users (that's what userprio is used for) it only (kind of) sorts the jobs inside ones batch of submitted jobs therefore it defaults to zero - which means nor priorities inbetween jobs.

Christoph is, of course, correct here. Something that is confusing about HTCondor is that we informally call the schedd a "queue", or that it holds a "queue" of jobs, but HTCondor does NOT, in a mathematical sense, schedule in a strict queue, for a number of reasons. Jobs that worker nodes prefer may "jump the queue", jobs that match now will start running before larger jobs that may only match on machines that are currently busy, etc.