These are all just turning into declarations in your local resource
manager's submission language. If you're using pbs, for instance, you
can see the RSL->PBS translation code in $GLOBUS_LOCATION/lib/perl/
Globus/GRAM/JobManager/pbs.pm.
For instance, for max_memory, you can see the following line:
print JOB "#PBS -l mem=${max_memory}mb\n";
It's possible that the way min_memory is being treated is incorrect
for your cluster, in which case this jobmanager perl script is the
appropriate place to change the translation.
Oddly, in the pbs.pm I looked at, I don't even see any treatment of
min_memory, only max_memory.
Charles
On Apr 25, 2008, at 1:16 PM, Steve White wrote:
Hi,
We also saw the "minMemory" tag. Document looks good.
Value is megabytes, tries to get that much per process, fails
otherwise.
I tried a couple of things and the results were bizarre.
1) If I specify a minMemory greater than the machine really has, it
does not fail, it happily executes.
2) Increasing the minMemory *increases* the number of processes run.
What?
- - - - - - - - - - - - - - - - - - - - - - -
- -
Steve White
+49(331)7499-202
e-Science / AstroGrid-D Zi. 35
Bg. 20
- - - - - - - - - - - - - - - - - - - - - - -
- -
Astrophysikalisches Institut Potsdam (AIP)
An der Sternwarte 16, D-14482 Potsdam
Vorstand: Prof. Dr. Matthias Steinmetz, Peter A. Stolz
Stiftung privaten Rechts, Stiftungsverzeichnis Brandenburg: III/
7-71-026
- - - - - - - - - - - - - - - - - - - - - - -
- -
