90 CPU-hour quota and accounting

CPU quota.

To use the batch system you have to have a cpu quota, either local or natinoal. For every job you submit we check that you have sufficient quota to run it and you will get a warning if you do not have sufficient cpu-hours to run the job. The job will be submitted to queue, but will not start until you have enough cpu-hours to run it.

Resource charging.

The accounting system charges for used processor equivalents (PE) times used walltime so if you ask for more than 2GB of memory per cpu you will get charged for more than the actual cpus you use.

Processor equivalents.

The best way to describe PE is maybe by example: Assume that you have a node with 8 cpu-cores and 16 GB memory (as most nodes on stallo are):

if you ask for less than 2GB memory per core then PE will equal the cpu count.

if you ask for 4GB memory per core then PE will be twice the cpu-count.

if you ask for 16GB memory then PE=8 as you only can run one cpu per compute node.

Inspecting your quota.

You can use the cost command to check how much cpu-hours are left on your allocation:

[user@stallo-1 ~]$ cost
Id  Name    Amount    Reserved Balance  CreditLimit Deposited Available Percentage
--- ------- --------- -------- -------- ----------- --------- --------- ----------
272 nnXXXXk 168836.65 96272.00 72564.65        0.00 290000.00  72564.65 58.22
10  nnYYYYk   4246.04     0.00  4246.04        0.00 150000.00   4246.04 2.83

The column meaning is

Inspecting historic use.

You can view the accounting history of your projects using:

gstatement --hours --summarize -s YYYY-MM-DD -e YYYY-MM-DD -p nnXXXXk

for more detail see:

gstatement --man