NEMO Status and Usage

NEMO: normal operation

Published: 6 Jul 2022 by HPC Team Freiburg

Security update July applied (CentOS 7.9, Rev. 21).
See update log for timestamps /opt/bwhpc/os-revisions/security_update_2022-07.

NEMO Queue

The following diagrams show the current status of the NEMO queue. These diagrams give only a rudimentary estimate of the current status of the queue. The start of each job depends on the current cluster utilization, the resource requirements of the job and the historical usage (fairshare).

The outer line of this graph shows the available cores for jobs in %. All nodes, including GPU nodes and nodes for interactive jobs, are used for this calculation. The inner line shows all idle jobs and the cores they require as a percentage (see Nemo Job Cores for absolute numbers). Fairshare, job priorities and special job requirements are not considered in this image.

This diagram shows the current cluster utilization and how many resources will be free in the next 6h, 12h, 24h and 48h. Jobs reserve resources for a certain time, which is specified when the job is placed. The remaining runtime of jobs is calculated and displayed in this diagram. Normally, jobs end earlier than the reserved time, so only the worst case is shown here.

These are the current job core numbers in the NEMO queue. Jobs are usually temporarily blocked because some dependencies are not met or a user exceeds a usage limit and are automatically moved to the idle job queue once the running jobs are finished. Please run showq -b -v or checkjob -v JobID on the cluster to determine the reason for the block.

These are the current job numbers in the NEMO queue. Jobs are usually temporarily blocked because some dependencies are not met or a user exceeds a usage limit and are automatically moved to the idle job queue once the running jobs are finished. Please run showq -b -v or checkjob -v JobID on the cluster to determine the reason for the block.

This is the NEMO job queue. (*) EST in the queue shows the expected start time for the job with the highest priority. Jobs are usually temporarily blocked because some dependencies are not met or a user exceeds a usage limit and are automatically moved to the idle job queue once the running jobs are finished. Please run showq -b -v or checkjob -v JobID on the cluster to determine the reason for the block.

NEMO Usage Statistics

NEMO Project Usage