[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Filling pool breadth-first with partitionable slots
- Date: Wed, 02 Nov 2016 10:50:39 -0500
- From: Tom Downes <downes@xxxxxxx>
- Subject: Re: [HTCondor-users] Filling pool breadth-first with partitionable slots
The manual (going off 8.5.7) is extremely unclear as to the benefits of CONSUMPTION_POLICY that you describe. As it stands, the macro's definition basically looks like a startd-side rounding mechanism with no implications about scheduling efficiency.
If you get to p. 383 you see some of the implications but the name CONSUMPTION_POLICY certainly doesn't lead one to conclude "this is a knob that makes scheduling better."
If you poke hard you'll find a release note for 8.2.8 that describes the conflict between CONSUMPTION_POLICY and CLAIM_PARTITIONABLE_LEFTOVERS. Are you asserting that enabling CONSUMPTION_POLICY is the more efficient of the two options? I read the manual to mean that CLAIM_PARTITIONABLE_LEFTOVERS defaults to True in a way that enables its use out-of-the-box.