Content
| Inhalt | type | flat
|---|
Project account
The NHR center NHR@ZIB follows NHR-wide regulations.
- A user User Account accesses a project account containing units of core hour. A project account can be a Test Project or a Compute Project.
- A batch job on the compute system is charged by a number of core hour to measure the compute timeusage.
- Usage of persistent storage including the tape library are currently not accounted.
Charge
...
rates
...
standard96
standard96:test
...
large96
large96:test
...
NHR@ZIB operates system Lise which hold with different Compute Partitions containing different types of compute nodes each. The charge rates for the partitions are given in the table.
...
partitions. Properties for available (slurm-)partitions you find on the pages
Each partition holds a specific charge rate.
| Compute partition | Slurm partition | Charge (core hour) per 1 node per 1 h occupancy time | Remark |
|---|---|---|---|
cpu-clx | 96 | ||
| cpu-clx:test | |||
| cpu-clx:ssd | |||
cpu-clx:large | 144 | high memory layouthuge96 | |
| cpu-clx:huge | 192 | high memory layout | |
| CPU Genoa partition | cpu-genoa cpu-genoa:test | free of charge1 | test phase |
| GPU A100 partition | 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 21.43 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) | |
| GPU PVC partition | gpu-pvc | free of charge1 | test phase |
...
1: Practically the charge is a very small number (close to zero).
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
...
| Panel | ||
|---|---|---|
| ||
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. |
Project accounts for batch jobs
The core hour to run a batch job are stored in a project account the User Account has access to.
- Test Project linked to the User Account
- Compute 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.
| Codeblock | ||
|---|---|---|
| ||
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:
| Codeblock | ||
|---|---|---|
| ||
| You can check the account of a job that is out of core hour. > squeue ... myaccount ... AccountOutOfNPL ... |