Thank you, i thought about that option but wasn't sure. It looks like working fine!
Cheers! ________________________________________ From: Christopher Samuel [[email protected]] Sent: Monday, July 25, 2016 3:23 AM To: slurm-dev Subject: [slurm-dev] Re: No limits on the allocated --mem option per node On 24/07/16 22:34, Igor Chebotar wrote: > SelectTypeParameters=CR_CPU To enforce memory you want: SelectTypeParameters=CR_CPU_Memory instead. From the slurm.conf manual page: CR_CPU_Memory CPUs and memory are consumable resources. Configure the number of CPUs on each node, which may be equal to the count of cores or hyper-threads on the node depending upon the desired minimum resource allocation. The node’s Boards, Sockets, CoresPerSocket and ThreadsPerCore may optionally be configured and result in job allocations which have improved locality; however doing so will prevent more than one job being from being allocated on each core. Setting a value for DefMemPerCPU is strongly recommended. Hope this helps.. Chris -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: [email protected] Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci=
