Hi Mr. Reuti , I set h_vmem equal to 48G and nodes have 48 slots (1G per slot). I mean that users request h_vmem at most 1G(this value is h_vmem per slot).If users can request more than 1G, some cores will be locked. I want to prevent such users at submission time to not happen locking other cores.
Thx On Tue, Dec 13, 2011 at 9:57 PM, Reuti <[email protected]> wrote: > Hi, > > Am 13.12.2011 um 11:46 schrieb mahbube rustaee: > > > Hi all, > > I 'm so thankful in advance. > > I set h_vmem to physical memory on host level. > > suppose current state of a node with 4G h_vmem and 4 free slots. > > a job with -l h_vmem=2G and pe mpi 2 launch to scheduler. > > In this case job is running , h_vmem on that node will be zero and 2 > cores of the node can't be used! > > Yep, this is the purpose of making it consumable. What behavior would you > like - when the job needs 4 GB, other jobs can't run there. Why would you > like to run additional jobs there? > > > > 2) How can I limit h_vmem request for any node at submission time ( > whereas h_vmem on host is total and request is per slots for any job)? > > It's not implemented to have it one time per host. It was foreseen when > the complexes got the new attribute "JOB", but it was never implemented for > now. You will have to divide it by hand beforehand. > > I also don't understand you request, you want to submit with "-l > h_vmem=2G", ok. It's per slot. So it will be multiplied and the result > subtracted from the available memory. So it's per host already. > > -- Reuti
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
