| 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 |
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
...
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.
...