IIRC this bug had to do with setting your "consumable" value to "YES" vs
"JOB". I think it only affected you if you have your consumable value
per job instead of per slot.
I have now:
#name shortcut type relop requestable consumable
default urgency
h_vmem h_vmem MEMORY <= YES YES
1G 0
We used to use "JOB" in that consumable column.
On 05/09/2016 02:13 AM, [email protected] wrote:
Hi,
We are running OGS/GE 2011.11p1. Concerning the problem that for certain
multi-core jobs the reported h_vmem value is much higher than the true
amount of memory used by the job, can anyone propose a solution to this
problem, e.g. working patch, … How do you deal with this problem? We
want to keep h_vmem consumable to prevent jobs from overbooking a node.
Thank you,
Nico
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
--
Alex Chekholko [email protected]
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
