Re: [OMPI users] memory limits on remote nodes

2010-10-12 Thread Ralph Castain
No problem - I got to learn something too! On Oct 11, 2010, at 11:19 PM, David Turner wrote: > Hi, > > Various people contributed: > > Isn't it possible to set this up in torque/moab directly? In SGE I would > simply define h_vmem and it's per slot then; and with a tight integration

Re: [OMPI users] memory limits on remote nodes

2010-10-12 Thread David Turner
Hi, Various people contributed: Isn't it possible to set this up in torque/moab directly? In SGE I would simply define h_vmem and it's per slot then; and with a tight integration all Open MPI processes will be children of sge_execd and the limit will be enforced. I could be wrong, but I -th

Re: [OMPI users] memory limits on remote nodes

2010-10-08 Thread Ralph Castain
Ah - I was unfamiliar with that option. Thanks! David: does that meet the need? On Oct 8, 2010, at 2:45 AM, Reuti wrote: > Am 08.10.2010 um 00:40 schrieb Ralph Castain: > >> >> On Oct 7, 2010, at 2:55 AM, Reuti wrote: >> >>> Am 07.10.2010 um 01:55 schrieb David Turner: >>> Hi, >>

Re: [OMPI users] memory limits on remote nodes

2010-10-08 Thread Reuti
Am 08.10.2010 um 00:40 schrieb Ralph Castain: > > On Oct 7, 2010, at 2:55 AM, Reuti wrote: > >> Am 07.10.2010 um 01:55 schrieb David Turner: >> >>> Hi, >>> >>> We would like to set process memory limits (vmemoryuse, in csh >>> terms) on remote processes. Our batch system is torque/moab. >> >

Re: [OMPI users] memory limits on remote nodes

2010-10-07 Thread Ralph Castain
On Oct 6, 2010, at 11:25 PM, David Turner wrote: > Hi Ralph, > >> There is an MCA param that tells the orted to set its usage limits to the >> hard limit: >> >> MCA opal: parameter "opal_set_max_sys_limits" (current >> value:<0>, data source: default value) >>

Re: [OMPI users] memory limits on remote nodes

2010-10-07 Thread Ralph Castain
On Oct 7, 2010, at 2:55 AM, Reuti wrote: > Am 07.10.2010 um 01:55 schrieb David Turner: > >> Hi, >> >> We would like to set process memory limits (vmemoryuse, in csh >> terms) on remote processes. Our batch system is torque/moab. > > Isn't it possible to set this up in torque/moab directly? I

Re: [OMPI users] memory limits on remote nodes

2010-10-07 Thread Reuti
Am 07.10.2010 um 01:55 schrieb David Turner: > Hi, > > We would like to set process memory limits (vmemoryuse, in csh > terms) on remote processes. Our batch system is torque/moab. Isn't it possible to set this up in torque/moab directly? In SGE I would simply define h_vmem and it's per slot t

Re: [OMPI users] memory limits on remote nodes

2010-10-07 Thread David Turner
Hi Ralph, There is an MCA param that tells the orted to set its usage limits to the hard limit: MCA opal: parameter "opal_set_max_sys_limits" (current value:<0>, data source: default value) Set to non-zero to automatically set any system-imposed li

Re: [OMPI users] memory limits on remote nodes

2010-10-06 Thread Ralph Castain
There is an MCA param that tells the orted to set its usage limits to the hard limit: MCA opal: parameter "opal_set_max_sys_limits" (current value: <0>, data source: default value) Set to non-zero to automatically set any system-imposed limits to the ma

[OMPI users] memory limits on remote nodes

2010-10-06 Thread David Turner
Hi, We would like to set process memory limits (vmemoryuse, in csh terms) on remote processes. Our batch system is torque/moab. The nodes of our cluster each have 24GB of physical memory, of which 4GB is taken up by the kernel and the root file system. Note that these are diskless nodes, so no