DokuWiki

User Tools

Site Tools

Trace: • usg_intern • 109 • 182 • 83 • 153 • 35 • 92
cluster:140

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
cluster:140 [2015/06/17 19:51] – hmeijcluster:140 [2015/12/04 18:53] (current) – [tinymem] hmeij
Line 12: Line 12:
  
 ===== tinymem ===== ===== tinymem =====
 +
 +Note: the tinymem queue is now only n46-n59 and the hp12 queue is back as before
 + --- //[[hmeij@wesleyan.edu|Meij, Henk]] 2015/12/04 13:52//
 +
  
 Since the hp12 nodes also have a small memory foot print we can merge this into the ''tinymem'' queue as an experiment. If it does not work, we'll bring it back in original configuration. With hyper threading on these nodes have 12 GB of memory for 16 logical cores or 0.75 GB/core. Since the hp12 nodes also have a small memory foot print we can merge this into the ''tinymem'' queue as an experiment. If it does not work, we'll bring it back in original configuration. With hyper threading on these nodes have 12 GB of memory for 16 logical cores or 0.75 GB/core.
Line 27: Line 31:
   * #BSUB -R "rusage[tmslow=1]"   * #BSUB -R "rusage[tmslow=1]"
  
-You need to request a consumable for each job slot, so if using say #BSUB -n 4 the '1' becomes a '4'.  And your job will go PENDing when consumables are exhausted. When would you do this? For example if you do not wish to run on the hptmnodes and are ok with waiting, or if the fabulous new hardware is clogged full of jobs and you wish to immediately bypass those.+You need to request a consumable for each job slot, so if using say #BSUB -n 4 the '1' becomes a '4'.  And your job will go PENDing when consumables are exhausted. When would you do this? For example if you do not wish to run on the hptmnodes and are ok with waiting, or if the fabulous new hardware is clogged full of jobs and you wish to immediately bypass those. Or, for now, the old hardware is running redhat 5 and the new centos 6.
  
-Doing nothing, that is not using or requesting consumabels, is a perfect strategy too.+Doing nothing, that is not using or requesting consumables, is a perfect strategy too.
  
 Today queues ''hp12'' is closed while we wait for it to empty out. Then it disappears. Today queues ''hp12'' is closed while we wait for it to empty out. Then it disappears.
Line 40: Line 44:
   * ssh node_name top -u user_name -b -n 1   * ssh node_name top -u user_name -b -n 1
  
-**Use top, remotely, in batch.** Look at the VIRT for memory usage the OS thinks you need, if that exceeds the node capacity go to other queues. For example+**Use top, remotely, in batch.** Look at the VIRT for memory usage the OS thinks you need, if that exceeds the node capacity go to other queues. For example (not picking on anybody!)
  
 <code> <code>
Line 62: Line 66:
  
 # and here is a problem, at 10.8 GB per java process # and here is a problem, at 10.8 GB per java process
-# the new hardware can only 3 of these jobs and  +# the new hardware can only handlew 3 of these jobs (32gb max) and  
-# the old hardware can only run 1 of these  +# the old hardware can only run 1 of these (12 gb max) 
-# so you need to either reserve memory in advance (see below) +# so you need to either reserve memory in advance (see below) or 
-# or move to another queue like mw256 (and also reserve memory)+# (better) move to another queue like mw256 (and also reserve memory)
  
 [hmeij@greentail ~]$ ssh n58 top -u cjustice -b -n 1                                                           [hmeij@greentail ~]$ ssh n58 top -u cjustice -b -n 1                                                          
cluster/140.1434570681.txt.gz · Last modified: by hmeij