NEMO Status and Usage

NEMO: normal operation

Published: 6 Oct 2021 by HPC Team Freiburg

Security update October applied (CentOS 7.9, Rev. 12).
See update log for timestamps /opt/bwhpc/os-revisions/security_update_2021-10.

NEMO Queue

The following graphs show the current status of the NEMO queue. These graphs just give some rudimentary estimation of the current queue state. The start of individual jobs depends on the current cluster usage, the ressource requirements of the job and 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 their corresponding cores, which are waiting to be executed (see Nemo Job Cores for absolute numbers). Fairshare, job priorities and special job requirements are not displayed in this image.

This graph shows the current cluster usage and how many resources are freed within the next 6h, 2h, 24h and 48h. Jobs reserve resources for an amount of time which is predefined at job submit. The remaining reservation time is calculated and displayed in this graph. Usually jobs end earlier than the reserved walltime.

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

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

This is the NEMO job queue. (*) EST in the idle queue indicates the estimated starting time for the job with the highest priority. Jobs are usually only temporary blocked because some dependencies are not met or a user exceeds a usage limit and will be moved to the idle queue automatically once running jobs finish. Please run showq -b -v or checkjob -v JobID on the cluster on the cluster for the block reason.

NEMO Usage Statistics

NEMO Project Usage