This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
cluster:116 [2013/08/06 19:27] hmeij |
cluster:116 [2014/02/04 18:57] (current) hmeij |
||
---|---|---|---|
Line 1: | Line 1: | ||
\\ | \\ | ||
**[[cluster: | **[[cluster: | ||
+ | |||
+ | Since deployment of sharptail the information below is out of date. /home is now the same across the entire HPCC and served out by sharptail. | ||
+ | |||
+ | --- // | ||
===== Sharptail Cluster ===== | ===== Sharptail Cluster ===== | ||
Line 39: | Line 43: | ||
==== /sanscratch ==== | ==== /sanscratch ==== | ||
- | Sharptail will provide the users (and scheduler) with another 5 TB scratch file system. | + | Sharptail will provide the users (and scheduler) with another 5 TB scratch file system. |
* Please offload as much IO from /home by staging your jobs in /sanscratch | * Please offload as much IO from /home by staging your jobs in /sanscratch | ||
Line 78: | Line 82: | ||
In both cases you do not need to target any specific core, the operating system will handle that part of the scheduling. | In both cases you do not need to target any specific core, the operating system will handle that part of the scheduling. | ||
+ | |||
+ | ==== NOTE ==== | ||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | Instructions below are obsolete, resources are now available via the scheduler. | ||
+ | |||
+ | Please read [[cluster: | ||
+ | |||
+ | --- // | ||
+ | |||
+ | ---- | ||
Line 253: | Line 270: | ||
# you only need one cpu core | # you only need one cpu core | ||
- | [hmeij@sharptail nucleosome]$ mpirun_rsh -ssh -hostfile ~/ | + | [hmeij@sharptail nucleosome]$ mpirun_rsh -ssh -hostfile ~/ |
+ | / | ||
</ | </ |