[GE users] Strange Consequence of Changing h_vmem .. N1GE 6.1

Reuti reuti at staff.uni-marburg.de
Sun Sep 30 18:43:16 BST 2007


Am 30.09.2007 um 04:57 schrieb Graham Jenkins:

> On Sat, 2007-09-29 at 16:10 +0200, Reuti wrote:
>
>> With h_vmem also h_data and h_stack will be set. Some applications
>> need the limit to be smaller, i.e. if h_vmem & h_stack is infinity
>> all is fine, but if h_vmem is set, h_stack needs considerably
>> smaller, around 128M is often fine.
>>
>> Any changes when you try this?
>
> Thanks Reuti, that solves my initial problem (for an Intel Fortran
> OpenMPI job) running on a special Test queue (on our 4G machine with 2
> CPUs and therefore 2 Slots) thus:
> --
> qconf -sq tque |grep "h_"
> h_rt                  00:04:00
> h_cpu                 INFINITY
> h_fsize               INFINITY
> h_data                INFINITY
> h_stack               128m
> h_core                INFINITY
> h_rss                 INFINITY
> h_vmem                2g
> --
> #!/bin/sh
> #$ -S /bin/sh
> #$ -pe mpich 2
> #$ -cwd
> . /etc/profile
> module load openmpi-intel
> mpirun -np 2 ../bin/pi3a 123  => works as expected!
> --
>
> But it creates another problem thus:
> --
> #!/bin/sh
> #$ -S /bin/sh
> #$ -cwd
> module load java
> java -Xms1800m -Xmx1801m -jar ../bin/bigpi.jar 123
> --
> cat bigpi.sh.[oe]14866
> Could not create the Java virtual machine.
> Error occurred during initialization of VM
> Could not reserve enough space for object heap
> --
>
> So I guess I really need to know more about the relationship between
> h_vmem, h_stack and h_data on an AMD64 2-cpu machine running something
> like RHEL5.  Are you able to assist please .. or better still,  
> suggest a
> mechanism which will prevent a user of any Application (Java, Fortran,
> NAMD, Octave, etc.) from grabbing more than 2gb of memory .. without
> otherwise restricting such a user?

You can check this with the "ulimit -aH" in your jobscript: h_vmem  
will also set h_data and h_stack. For now I would suggest to increase  
h_stack a little bit to 256M.

h_vmem is the right way to go to limit memory consumption.

-- Reuti


> -- 
> Graham Jenkins
> Senior Software Specialist, E-Research
>
> Email: Graham.Jenkins at its.monash.edu.au
> Tel:   +613 9905-5942
> Mob:   +614 4850-2491
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list