Changes between Version 3 and Version 4 of Doc/env/TgccCurie


Ignore:
Timestamp:
07/23/14 16:17:32 (10 years ago)
Author:
aclsce
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/env/TgccCurie

    v3 v4  
    148148 
    149149## SSD on standard node : how to use it for rebuild job ## 
    150 SSD usage could accelerate rebuild job. It's very usefull for medium and high resolution configuration like IPSLCM5A-MR. You have only to change header and RUN_DIR_PATH in rebuild.job. Take care you will run faster but cost will be multiplicated by a factor of 16 because standard node ie 16 cpus are dedicated. 
     150SSD usage could accelerate rebuild job. It's very usefull for medium and high resolution configuration like IPSLCM5A-MR. You have only to change header and RUN_DIR_PATH in rebuild.job. Take care you will run faster but cost will be multiplicated by a factor of 16 because standard node ie 16 cpus are dedicated. Beware of the size of the /tmp (64GB/node) : if you have configuration with very high resolution and very high output frequency, the /tmp of standard node could be too small; in this case see below. 
    151151 
    152152{{{ 
     
    154154#MSUB -x  # exclusive node 
    155155RUN_DIR_PATH=/tmp/REBUILD_DIR_MR_$$ 
     156}}} 
     157 
     158## RAM on fat node : how to use it for rebuild job ## 
     159If /tmp of standard node (64GB) is too small for you, you can use fat node. You have to know the /tmp of fat node is also of 64GB. You have to use the RAM disk which is 250GB/node. You have only to change header and RUN_DIR_PATH in rebuild.job. Take care you will run faster but cost will be multiplicated by a factor of 128 because fat node ie 128 cpus are dedicated. 
     160 
     161{{{ 
     162#MSUB -q xlarge # thin nodes 
     163#MSUB -x  # exclusive node 
     164RUN_DIR_PATH=/dev/shm/REBUILD_DIR_MR_$$ 
    156165}}} 
    157166