Hi community,
I set complex /h_vmem/ consumable with default 2.0G and per exec host
the physical limit to 46G, as well /virtual_free (vf)/ is set
consumable, default 1G and per exec host is as well 46G.
Some users have advantage of using openmp and openmpi mixed in their
jobs. To reduce the waste of allocated memory and to reduce the "qw"
time of the jobs I have to understand the behavior of the gridengine in
mixed parallel jobs.
First of all /h_vmem/ is per slot ( as well per core ?) In case of
openmp threads which are not part of the $NSLOTS, must be the amount of
RAM multiplied with OMP_NUM_THREADS or not ?
Secondly, if the user defines in the job as well /vf/ and /h_vmem/, what
consumable is used by the gridengine to find suitable machines to start
the jobs ? Without /h_vmem/, the /vf/ is used this I now and is written
in the documentation, but when I have defined/h_vmem/ as well is then
/vf/ ignored ?/
//pe:
pe_name openmp_6
slots 3168
user_lists standard
xuser_lists NONE
start_proc_args /bin/true
stop_proc_args /bin/true
allocation_rule 6
control_slaves TRUE
job_is_first_task FALSE
urgency_slots min
accounting_summary FALSE/
job script:
/#$ -N test
#$ -cwd
#$ -o $JOB_ID.out
#$ -e $JOB_ID.err
#$ -l h_rt=150:00:00
#$ -l vf=2.3G
#$ -l h_vmem=3G
#$ -pe openmp_6 72
export OMP_NUM_THREADS=6
export MKL_NUM_THREADS=($OMP_NUM_THREADS)
mpirun --mca btl openib,self -pernode -np 12 /my_mixed_job/
Udo
--
Udo Schmidt
Max-Planck-Institut für Mikrostrukturphysik
Weinberg 2, 06120 Halle (Saale), Germany http://www.mpi-halle.de/~theory
Phone: +49 345 5582541 Fax: +49 345 5582765 Email: [email protected]
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
