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

Re: [HTCondor-users] Partitonable slots + memory/swap constraints


I happened to give a talk on precisely this topic at HTCondor Week (ongoing right now). PDF in link below. My talk was aimed at systemd distros but most of the concepts can be applied to init-based systems as well.


Tom Downes
Senior Scientist and Data CenterÂManager
Center for Gravitation, Cosmology and Astrophysics
University of Wisconsin-Milwaukee

On Thu, May 4, 2017 at 3:11 PM, Zimmermann, Nikolas <zimmermann@xxxxxxxxxxxxxxxxxxxxx> wrote:
Dear all,

Weâre trying to setup partionable slots with constraints on physical memory + swap usage.
ForÂpartitionable slots these limits do NOT seem to be enforced with HTcondor 8.4 / 8.6 (we tried upgrading recently, without luck).

The same question was already asked in February this year:Âhttps://lists.cs.wisc.edu/archive/htcondor-users/2017-February/msg00055.shtml
Unfortunately nobody replied to this.

This is a real show-stopper for our institute - since we switched to partitonable slots to allow multi-core jobs to run, the cgroup policies can no longer be enforced.

We ideally want condor/cgroups to enforce the physical RAM usage, and only allow for a certain amount of swap to be used for each job (slot).
If any of the pre-defined (or user-requested) limits are reached, the job shall be killed.

Weâd highly appreciate any help!

Thanks in advance,

Nikolas Zimmermann
RWTH Aachen University of Technology

Phone: +49-241-80-27205
Address: I. Physikalisches Institut B,ÂSommerfeldstr. 14, D-52074 Aachen

HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@cs.wisc.edu with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: