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

Re: [HTCondor-users] HTCondor/cgroups: limiting CPUs/pinning processes to CPUs with hyperthreaded CPUs

Hi Michael,

yes - I had some hands on with cgroups on Univa SGE and they really got
Actually, my original question arose, when I noticed a user complaining
in another mailing list, that his jobs got killed at another site -
rightly, I guess, since he was running a 'make -j32' while requesting
one core...

I really am looking forward to let cgrougs take care of such human forms
as your Matlab cases and do not have to worry much about
thread/memory/... bombs anymore ;)

Cheers and thanks,

On 2016-02-04 17:01, Michael V Pelletier wrote:
> From: Thomas Hartmann <thomas.hartmann@xxxxxxx>
> Date: 02/04/2016 10:46 AM
>> many thanks for the info!
>> I have not considered CPU time sharing/known about its implementation in
>> HTCondor/cgroups. Using cpu shares should get a much better resource
>> utilization than pinning ;)
> I was a very early adopter of cgroups right from 8.0 back in 2013, and
> love 'em. I suspect you will too. At least a couple of the cgroup bug
> tickets
> originated with me, both at CHTC and Red Hat. ;D
> They're really an essential element of exec node self-defense, and
> made a big difference in the uptime numbers back when we were still working
> on disciplining some of our misbehaving jobs.
>         -Michael Pelletier.
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature