Skip to content
Snippets Groups Projects
Commit cfdc27ae authored by Branislav Jansik's avatar Branislav Jansik
Browse files

Update resource_accounting.md

parent 4db394b6
No related branches found
No related tags found
6 merge requests!368Update prace.md to document the change from qprace to qprod as the default...,!367Update prace.md to document the change from qprace to qprod as the default...,!366Update prace.md to document the change from qprace to qprod as the default...,!323extended-acls-storage-section,!196Master,!159Bjansik
......@@ -3,28 +3,33 @@
### Wall-clock Core-Hours WCH
The wall-clock core-hours (WCH) are the basic metric of computer utilization time.
1 wall-clock core-hour is defined as 1 processor core allocated for 1 hour of wall-clock time. Allocating a full node (24 cores)
for 1 hour amounts to 24 wall-clock core-hours.
1 wall-clock core-hour is defined as 1 processor core allocated for 1 hour of wall-clock time. Allocating a full node (16 cores Anselm, 24 cores Salomon)
for 1 hour amounts to 16 wall-clock core-hours (Anselm) or 24 wall-clock core-hours (Salomon).
### Standard Core-Hours SCH
The resources subject to accounting are the standard core-hours (SCH).
The standard core-hours are obtained from WCH by applying a standardization factor:
---8<--- "sch_formula.md"
$$
SCH = F*WCH
$$
The accounting runs whenever the computational cores are allocated via the PBS Pro workload manager (the qsub command), regardless of whether
the cores are actually used for any calculation. All jobs are accounted in standard core-hours, using factor F valid at the time of the execution:
All jobs are accounted in standard core-hours, using factor F valid at the time of the execution:
| System | F | Validity |
| ------------------------------- | - | -------- |
| Salomon | 1.00 | 2017-09-11 to 2018-06-01 |
| Anselm | 0.65 | 2017-09-11 to 2018-06-01 |
!!! note
The allocations are requested/granted in standard core-hours SCH.
The accounting runs whenever the computational cores are allocated via the PBS Pro workload manager (the qsub command), regardless of whether
the cores are actually used for any calculation.
Whenever the term core-hour is used in this documentation, we mean the standard core-hour, SCH.
!!! note
*The allocations are requested/granted in standard core-hours SCH.
*Whenever the term core-hour is used in this documentation, we mean the standard core-hour, SCH.
The standard core-hours were introduced to treat systems of different age on equal footing.
Standard core-hour is an accounting tool to discount the legacy systems. The past (before 2017-09-11) F factors are all 1.0.
......@@ -34,7 +39,7 @@ See examples in the [Job submission and execution](job-submission-and-execution/
### Consumed Resources
User may check at any time, how many core-hours have been consumed by himself/herself and his/her projects. The command is available on cluster login nodes.
Check how many core-hours have been consumed. The command it4ifree is available on cluster login nodes.
```console
$ it4ifree
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment