The NHR center NHR@ZIB follows NHR-wide regulations.
- A user accesses an account containing units of core hour to measure compute time.
- Batch jobs on the compute systems are charged by a number of core hour.
- Usage of persistent storage including the tape library are currently not accounted.
Charge Rates
NHR@ZIB operates system Lise which hold different Compute Partitions containing different types of compute nodes each. The charge rates for the partitions are given in the table.
| one node in partition | charged "core hours" per 1h occupancy time | increased charge rate due to |
|---|---|---|
standard96 standard96:test | 96 | |
large96 large96:test large96:shared | 144 | high memory layout |
| huge96 | 192 | high memory layout |
gpu-a100 | 600 | four NVidia A100 (80 GB) per compute node |
gpu-a100:shared | 150 per GPU | 600 for four NVidia A100 (80 GB) per node |
gpu-a100:shared:mig | 47 per MiG slice | four NVidia A100 (80 GB) splitted each into two 2g.10gb slices (8 per node and currently 24 in total) and one 3g.20gb slice (4 per node and currently 12 in total) |
Job Charge
The charge of core hours for a batch job depends on the number of nodes, the wallclock time used by the job, and the charge rate for the partition used. For a batch job with
a number of nodes n,
running with a wallclock time of t hours, and
- on a partition with a charge rate charge_p
the job charge charge_j yields
charge_j = n * t * charge_p
A job on 10 nodes running for 3 hours on partition huge96 (= 192 core hour) yields a job charge of 5760 core hour.
Batch jobs running in the partition large96:shared access a subset of cores on a node. For a reservation of cores, the number of nodes is the appropriate node fraction.
A job on 48 cores on partition large96:shared (96 cores per node, 144 core hour) has a reservation for
num = 48/96 = 0.5 nodes. Assuming a wallclock time of 3 hours yields a job charge of 216 core hour.
Account Types
Running batch jobs with a User Account, the user can access different accounts in general. The NHR centers distinguish between
- personal accounts and
- project accounts
Project Account
A compute project holds a bank account for the project. This project account contains a compute capacity in core hours. At the beginning of each quarter the account is granted by the number of core hours following the funding decision for the given compute project. A project account holds at least 4x300 k core hours per year. Unused core hours are transferred to the subsequent quarter, but only one time.
In case of problems with your compute capacity in core hours in your project account please contact your consultant. This might affect the
- application for additional core hours,
- movement of core hours between quarters.
Select the Account in Your Batch Job
Batch jobs are submitted by a user account to the compute system. For each job the user chooses the account that will be charged by the job.
For the user account the default account for compute time is defined on the link Informationen zu Ihrer Kennung/Account information of the service portal. At the beginning of the lifetime of the user account the default account is the personal account.
The user controls the account for a job using the Slurm option --account at submit time.
To charge the account myaccount add the following line to the job script. #SBATCH --account=myaccount
After job script submission the batch system checks the account for account coverage and authorizes the job for scheduling. Otherwise the job rejected, please notice the error message:
You can check the account of a job that is out of core hour. > squeue ... myaccount ... AccountOutOfNPL ...