Inhalt | ||
---|---|---|
|
...
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 |
medium40 medium40:test | 40 | |
large40 large40:test | 80 | high memory layout |
gpu | 375 | four NVidia V100 (32 GB) GPUs per node |
grete | 600 | four NVidia A100 (40 GB) |
grete:shared | 150 per GPU | 600: four NVidia A100 (40 GB) per node |
grete:interactive grete:preemptible | 47 per MiG slice | four NVidia A100 (40 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 for a batch job on the NHR systems is the number of core hours and is calculated from the number of nodes reserved for the job, the wallclock time used by the job, and the charge rate for the job nodes. For a batch job with
...
- personal accounts and
- project accounts
Personal Account
On the HLRN-IV NHR systems, each user account is attached to a bank account containing core hours. Both accounts, the user account and the bank account, share the same name but their purpose is different. The user account is the account of the Linux operation system and is used for authorization and access control incl. permissions to data files. The bank account is to limit the computing time.
...