User Tools

Site Tools


services:cluster:queuing-system

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
services:cluster:queuing-system [2012/10/18 17:25] pneuserservices:cluster:queuing-system [2014/06/11 14:40] (current) dreger
Line 1: Line 1:
-====== Introduction to the HPC cluster of the physics department ======+====== Introduction to the Torque HPC cluster of the physics department ======
  
 The login node of the HPC cluster is ''sheldon.physik.fu-berlin.de''. You can connect to it from anywhere using ssh, e.g. by issuing ''ssh sheldon.physik.fu-berlin.de'' on the command line or using putty from windows. The login node of the HPC cluster is ''sheldon.physik.fu-berlin.de''. You can connect to it from anywhere using ssh, e.g. by issuing ''ssh sheldon.physik.fu-berlin.de'' on the command line or using putty from windows.
Line 6: Line 6:
  
 ===== Getting information about cluster utilization ===== ===== Getting information about cluster utilization =====
 + 
 You can list the current workload on the HPC cluster using the command ''qf'':  You can list the current workload on the HPC cluster using the command ''qf'': 
  
Line 101: Line 101:
 | walltime | seconds, or [[HH:]MM:]SS | Maximum amount of real time during which the job can be in the running state. The job will be terminated once this limit is reached. | **walltime=100:00:00** -> request 100 hours for this job | walltime=1:00:00 (1 hour) | | walltime | seconds, or [[HH:]MM:]SS | Maximum amount of real time during which the job can be in the running state. The job will be terminated once this limit is reached. | **walltime=100:00:00** -> request 100 hours for this job | walltime=1:00:00 (1 hour) |
 | pmem | size* | Maximum amount of physical memory used by any single process of the job. In our case this means per core. | **pmem=8gb** -> request 8gb RAM per core | pmem=2gb | | pmem | size* | Maximum amount of physical memory used by any single process of the job. In our case this means per core. | **pmem=8gb** -> request 8gb RAM per core | pmem=2gb |
-| file | size* | The amount of **local disk space per core** requested for the job. The space can be accessed at /local_scratch/$PBS_JOBID | **file=10gb** -> request 10 gigabytes of local disk space on each compute node | none |+| file | size* | The amount of **local disk space per core per node** requested for the job. The space can be accessed at /local_scratch/$PBS_JOBID | **file=10gb** -> request 10 gigabytes of local disk space on each compute node for each core used on a node | none |
  
 **size* format** = integer, optionally followed by a multiplier {b,kb,mb,gb,tb} meaning {bytes,kilobytes,megabytes,gigabytes,terabytes}. no suffix means bytes. **size* format** = integer, optionally followed by a multiplier {b,kb,mb,gb,tb} meaning {bytes,kilobytes,megabytes,gigabytes,terabytes}. no suffix means bytes.
services/cluster/queuing-system.1350581128.txt.gz · Last modified: 2012/10/18 17:25 by pneuser

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki