[gridengine users] limit CPU/slot resource to the number of reserved slots

Dietmar Rieder dietmar.rieder at i-med.ac.at
Mon Aug 26 19:45:26 UTC 2019


thanks for your reply. This sounds promising.
We are using Son of Grid Engine though. Can you point me to the right
docs to get cgroup enabled in the exec host (CentOS 7). I must admit I
have no experience with cgroups.

Thanks again

On 8/26/19 4:03 PM, Skylar Thompson wrote:
> At least for UGE, you will want to use the CPU set integration, which will
> assign the job to a cgroup that has one CPU per requested slot. Once you
> have cgroups enabled in the exec host OS, you can then set these options in
> sge_conf:
> cgroup_path=/cgroup
> cpuset=1
> You can use this mechanism to have the m_mem_free request enforced as well.
> On Mon, Aug 26, 2019 at 02:15:22PM +0200, Dietmar Rieder wrote:
>> Hi,
>> may be this is a stupid question, but I'd like to limit the used/usable
>> number of cores to the number of slots that were reserved for a job.
>> We often see that people reserve 1 slot, e.g. "qsub -pe smp 1 [...]"
>> but their program is then running in parallel on multiple cores. How can
>> this be prevented? Is it possible that with reserving only one slot a
>> process can not utilize more than this?
>> I was told the this should be possible in slurm (which we don't have,
>> and to which we don't want to switch to currently).
>> Thanks
>>   Dietmar

D i e t m a r  R i e d e r, Mag.Dr.
Innsbruck Medical University
Biocenter - Institute of Bioinformatics
Email: dietmar.rieder at i-med.ac.at
Web:   http://www.icbi.at

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: OpenPGP digital signature
URL: <http://gridengine.org/pipermail/users/attachments/20190826/2ff3d7f2/attachment.sig>

More information about the users mailing list