| 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
...
Batch jobs are submitted by a user account to the compute system.
- For each job the user chooses
...
- one project 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 Portal NHR@ZIB. At the beginning of the lifetime of the user account User Account the default account project is the personal accountTest Project.
- The user controls the account project for a job using the Slurm option --account at submit time.
For the User Account the default project for computing time is defined on the link User Data on the Portal NHR@ZIB.
| Codeblock | ||
|---|---|---|
| ||
To charge the account myaccount add the following line to the job script. #SBATCH --account=myaccount |
...