Resource Usage
Balance and Billing
Billing is based on the used CPU core and/or GPU card hours on the supercomputer. Balance of the user’s projects (accounts) can be displayed using the sbalance command.
account |
CPU-core Hour usage |
CPU-core Hour limit |
GPU-card Hour usage |
GPU-card Hour limit |
my_project_01 |
1578 |
50000 |
0 |
0 |
my_project_02 |
7765 |
100000 |
130 |
312 |
The second column shows the computing time used in the projects in CPU core hours. The fourth column shows the computing time (hours) used on the GPU cards. The account limits are indicated in the third (CPU core hours) and the fifth (GPU card hours) columns.
Total Consumption
The sreport command (which also in the background of the previous sbalance python script) can be used to query details of the consumption since a particular date:
A report can be created for each user and each resource for a given timeframe (of the given account):
sreport -t Hours Cluster AccountUtilizationByUser Accounts=<ACCOUNT> Start=2024-01-01 End=2024-02-01 --tres=cpu,gres/gpu
Further information can be found in the manpages for sreport.
Storage Quotas
The total size and number of files that can be used by a user and project are limited on each storage tier.
Storage usage and the limits (quotas) can be checked using the squota command
(see also: “Storage / Overview”):
$ squota
account Filesystem used soft limit hard limit grace files soft limit hard limit grace
--------- ------------ -------- ------------ ------------ ----------- ------- ------------ ------------ -------
tesztuser /project 23.2 GB 20.0 GB 25.0 GB 6d11h19m36s 11215 100000 110000 -
tesztpro /project 4.0 KB 4.0 TB 4.4 TB - 1 1000000 1100000 -
tesztpro /scratch 4.0 KB 1.0 TB 1.1 TB - 1 300000 330000 -
Warning
If your application uses a large number of small files you can easily run out of inode (number of files) limits. For tips on how to handle this situation, see: “File management considerations / Inode Limit”