Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
doku:memory [2014/07/30 10:05] – [ad 1. node with more memory] irdoku:memory [2014/08/12 10:07] – [ad 2. parallel environment with fewer processes per node] ir
Line 24: Line 24:
 To use one of these nodes, just add '''-l mem_free=50G''' or '''-l mem_free=100G''' to ''qsub''. To use one of these nodes, just add '''-l mem_free=50G''' or '''-l mem_free=100G''' to ''qsub''.
  
-See also [[doku:memory_running_jobs|memory usage of running jobs!]]+See also [[doku:memory_running_jobs|memory usage of running jobs]]!
  
 ==== ad 2. parallel environment with fewer processes  per node ==== ==== ad 2. parallel environment with fewer processes  per node ====
  
-Jobs using more than 2 GB per core can be executed on one of the parallel environments +   *[[doku:ompmpi|Hybrid OpenMP/MPI jobs ]]
-  mpich84 GB per core +
-  * mpich4: 8 GB per core +
-  * mpich2: 16 GB per core +
-  * mpich1: 32 GB per core+
  
-Please keep in mind that on VSC-2 jobs are node-exclusive and therefore your contingent of CPU-hours will be computed by full nodes and are therefore significantly more expensive. 
-For example, <code>qsub -pe mpich2 64 my_job.sh</code> requests 64 cores, each with 16 GB: this is fulfilled by 32 nodes: each hour of this job costs 32*16=512 CPU-hours. 
- 
-The variable NSLOTS_REDUCED is set to the number of cores requested, whereas the variable NSLOTS is set to the number of cores allocated in the queueing system, which corresponds to the cost calculation of the previous paragraph. 
-Replace your calls to mpirun accordingly to<code>mpirun -n $NSLOTS_REDUCED ... </code> where applicable! 
  
 ==== ad 3. increased virtual memory ==== ==== ad 3. increased virtual memory ====
  • doku/memory.txt
  • Last modified: 2015/09/17 12:32
  • by jz