...
The accounting on the HPCF is currently based on the total elapsed time for which cores are used. With that, the HPCF unit of account, the System Billing Unit, or SBU, for both serial and parallel jobs is defined as follows.the cores allocated to serial or parallel batch jobs. To reflect the current system configuration and performance the formula to compute SBU will change on 1 January 2024 to:
where:
P = 424074479 / (8090 * 128 * 86400) | is a fixed proportionality factor, adjusted so that the entire Atos system will deliver 424,074,479 SBU per day on a "typical" ECMWF job mix on the HPC system (8090 * 128 is the total number of physical cores used to run batch jobs and 86400 the number of seconds in a day). |
N | Is the number of (physical) cores allocated to a job. |
T | is the elapsed time (real time in seconds) recorded for a job. |
Examples:
- A serial job using 1 hour (3600 seconds) of elapsed time will be charged about 17.06 SBU.
- A parallel job requesting 2 nodes, running for 3 hours elapsed time will be charged 13104.90 SBU.
Compared to 2023 the SBU cost of the same job in 2024 will be ~10.8% less .
Expand |
---|
|
where: P = 470410408 / (8098 * 128 * 86400) | is a fixed proportionality factor, adjusted so that the entire Atos system will deliver 470,410,408 SBU per day on a "typical" ECMWF job mix on the HPC system (8098 * 128 is the total number of physical cores used to run batch jobs and 86400 the number of seconds in a day). | N | Is the number of (physical) cores allocated to a job. | T | is the elapsed time (real time in seconds) recorded for a job. | Examples: - A serial job using 1 hour (3600 seconds) of elapsed time will be charged about 18.91 SBU.
- A parallel job requesting 2 nodes, running for 3 hours elapsed time will be charged 14522.43 SBU.
|
Tip |
---|
title | End of job information |
---|
|
At the end of your jobs a short report is appended to the corresponding job output file, which amongst other useful information, includes how many SBUs where used and the account they were charged on: No Format |
---|
[ECMWF-INFO -ecepilog] ----------------------------------------------------------------------------------------------------
[ECMWF-INFO -ecepilog] This is the ECMWF job Epilogue
[ECMWF-INFO -ecepilog] +++ Please report issues using the Support portal +++
[ECMWF-INFO -ecepilog] +++ https://support.ecmwf.int +++
[ECMWF-INFO -ecepilog] ----------------------------------------------------------------------------------------------------
[ECMWF-INFO -ecepilog] Run at 2022-08-24T09:09:01 on ac
[ECMWF-INFO -ecepilog] JobName : myjob
[ECMWF-INFO -ecepilog] JobID : 37015044
[ECMWF-INFO -ecepilog] Submit : 2022-08-24T09:08:55
[ECMWF-INFO -ecepilog] Start : 2022-08-24T09:08:55
[ECMWF-INFO -ecepilog] End : 2022-08-24T09:09:01
[ECMWF-INFO -ecepilog] QueuedTime : 0.0
[ECMWF-INFO -ecepilog] ElapsedRaw : 6
[ECMWF-INFO -ecepilog] ExitCode : 0:0
[ECMWF-INFO -ecepilog] DerivedExitCode : 0:0
[ECMWF-INFO -ecepilog] State : COMPLETED
[ECMWF-INFO -ecepilog] Account : myaccount
[ECMWF-INFO -ecepilog] QOS : np
[ECMWF-INFO -ecepilog] User : user
[ECMWF-INFO -ecepilog] StdOut : /home/user/slurm-37015044.out
[ECMWF-INFO -ecepilog] StdErr : /home/user/slurm-37015044.out
[ECMWF-INFO -ecepilog] NNodes : 1
[ECMWF-INFO -ecepilog] NCPUS : 256
[ECMWF-INFO -ecepilog] SBU : 4.083
[ECMWF-INFO -ecepilog] ---------------------------------------------------------------------------------------------------- |
|
SBU simulator
You can see how much your job would cost in terms of SBUs by copying and pasting here your job headers
...
.
Tip |
---|
title | Defining how long your job will run |
---|
|
Use the SLURM time directive for the job duration. For example, for a job that needs to run for 12 hours: #SBATCH --time=12:00:00 |
HTML Include |
---|
url | https://sites.ecmwf.int/udoc/sbu/simulator.html |
---|
|
What are my project accounts?
...