On 14-08-17 07:50, Lachlan Musicman wrote:
We have TaskPlugin=task/cgroup and when testing I noticed that the # of threads/cpus being allocated was rounded up to the nearest even. I presume this was due to cgroups marking a core as a cpu, rather than a thread as a cpu.
Sounds like you're using SelectTypeParameters=CR_Core[_Memory], where what you want requires SelectTypeParameters=CR_CPU[_Memory]?
I was hoping that the cgroup would kill the job because of too many cpus
task/cgroup just limits the CPUs available to a job; a job can still have any number of threads. (The number of *running* threads is of course limited to the number of available CPUs.)
Is it possible to have granular control at the thread level with cgroups?
Not that I know. Limiting the maximum number of threads can be done via resource limits.
Robbert
