DIRACGrid / DIRACGrid/DIRAC

Accounting [Jobs]: don't we need the wallclock time?

Open
#8,277 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
126
Forks
191
Avg merge
1d 13h
Merged PRs (30d)
33

Description

Right now we have `ExecTime` as `wall clock time * number of allocated cores`. Once this information is stored, it looks like we have no way to get back to `wall clock time` and `number of allocated cores`.

Out of curiosity, shouldn't we register `WallClockTime` and `NumberOfProcessors` as 2 separate values (that can then be derived to obtain the `ExecTime`).
We could potentially get statistics about the time to execute jobs and the number of processors they are using.

Also the term `Wall clock time` and its definition are widely adopted across batch systems I think, so it could potentially be more intuitive for the people that need to create reports from Accounting DB data for instance.

https://github.com/DIRACGrid/DIRAC/blob/09fdfae3fea92ad8be7614c4c562cc232d8bbbac/src/DIRAC/AccountingSystem/Client/Types/Job.py#L24-L26

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.