Skip to content

Billing policy

Running jobs on the compute nodes and storing data in storage space will consume the billing units allocated to your project:

  • Compute is billed (in most cases) in units of CPU-core-hours for CPU nodes, and in GPU-hours for GPU nodes (except for the lumid visualization partition, which is also billed in CPU-core-hours).
  • Storage space is billed in units of TB-hours.

How to check your billing units

To check how many billing units you have used, you can use the following command:

lumi-allocations

It will report the CPU-core-hours and GPU-hours allocated and consumed for all the projects you are a part of. The tool also reports the storage billing units.

A description of how the jobs are billed is provided in the next sections.

Compute billing

Compute is billed whenever you submit a job to the Slurm job scheduler.

CPU billing

For CPU compute, your project is allocated CPU-core-hours that are consumed when running jobs on the CPU nodes.
CPU billing applies to the Hardware partitions LUMI-C and LUMI-D, i.e. the compute partitions: standard, small, debug, largemem, and (starting from May 2026) the visualization partition lumid, are billed in CPU-core-hours.

Exclusive CPU partitions

The standard partition is operated in exclusive mode: it's not possible to reserve a part of a node on this partition, but entire nodes will always be allocated for your jobs. 128 CPU-core-hours are billed for every allocated node and per hour even if your job has requested less than 128 cores per node.

For example, allocating 16 nodes in a job running for 12 hours consumes:

16 nodes x 128 CPU-cores/node x 12 hours = 24576 CPU-core-hours

Non-exclusive CPU partitions

When using the partitions small, debug, or largemem, you are billed per allocated core. However, if you are above a certain threshold of memory allocated per core, you are billed per slice of 2GB memory (which is still billed in units of CPU-core-hours). Using the largemem partition of LUMI-D, or the high memory nodes in LUMI-C, is thus more expensive.

Specifically, the formula used for billing for these partitions is:

CPU-core-hours-billed = max(
  CPU-cores-allocated, ceil(memory-allocated / 2GB)
  ) x runtime-of-job

Thus,

  • if you use 2GB or less of memory per core, you are charged per allocated cores.
  • if you use more than 2GB of memory per core, you are charged per 2GB slice of memory.

For example, allocating 4 CPU-cores and 8GB of memory in a job running for 1 day consumes:

4 CPU-cores x 24 hours = 96 CPU-core-hours

Allocating 4 CPU-cores and 32GB of memory in a job running for 1 day consumes:

(32GB / 2GB) x 24 hours = 384 CPU-core-hours

Visualization partition lumid

The lumid visualization nodes located in LUMI-D hardware partition are billed in CPU-core-hours (since May 2026).

The formula for billing the lumid partitions is:

CPU-core-hours-billed = 
    max(
        ceil(CPU-cores-allocated / 16), 
        ceil(memory-allocated / 256 GB), 
        GCDs-allocated )
  * 64 * runtime-of-job

For example, a job allocating 1 GCD and running for 0.5 hours, consumes:

1 * 64 * 0.5 hours = 32 CPU-core-hours

If you allocate 1 GCD for 4 hours but allocate 512 GB of memory, then you are billed for this memory:

(512 GB / 256 GB) * 64 * 4 hours = 512 CPU-core-hours

GPU billing

For GPU compute, your project is allocated GPU-hours that are consumed when running jobs on the GPU nodes. A GPU-hour corresponds to the allocation of a full MI250x module (2 GCDs) for one hour, i.e. on LUMI-G, one node hour corresponds to 4 GPU-hours.
GPU billing applies to the Hardware partition LUMI-G, i.e. the compute partitions: standard-g, small-g, and dev-g, are billed in GPU-hours.

Exclusive GPU partitions

The partition standard-g is operated in exclusive mode: it's not possible to reserve a part of a node on this partition, but entire nodes will always be allocated for your jobs, and four MI250x GPU modules (8 GCD's) are thus billed for every allocated node even if your job has requested less than 8 GCD's per node.

For example, allocating 4 nodes and running for 24 hours consumes:

4 * 4 nodes * 24 hours = 384 GPU-hours

Non-exclusive GPU partitions

For the small-g and dev-g Slurm partitions, where allocation can be done at the level of Graphics Compute Dies (GCD's), you will be billed at a 0.5 rate per GCD allocated. However, if you allocate more than 8 CPU cores or more than 64 GB of memory per GCD, you will be billed per slice of 8 cores or 64 GB of memory.

The billing formula is:

GPU-hours-billed = (
    max(
        ceil(CPU-cores-allocated / 8),
        ceil(memory-allocated / 64GB),
        GCDs-allocated )
    * runtime-of-job) * 0.5

For example, a job allocating 2 GCDs and running for 24 hours consumes:

2 GCD's * 24 hours * 0.5 = 24 GPU-hours

If you allocate 1 GCD for 24 hours but allocate 128 GB of memory, then you will be billed for this memory:

(128 GB / 64 GB) * 24 hours * 0.5 = 24 GPU-hours

Storage billing

For storage, your project is allocated TB-hours. Storage is billed whenever you store data in your project folders. Storage is billed by volume used over time. The billing units are TB-hours.

The number of TB-hours billed depends on the type of storage you are using. See the data storage options page for an overview of the different storage options.

Main storage (LUMI-P) billing

The main storage backed by LUMI-P is billed directly as:

TB-hours-billed = storage-volume x time-used

For example, storing 1.2 TB of data for 4 days consumes:

1.2 TB x 24 hours/day x 4 days = 115.2 TB-hours

Flash storage (LUMI-F) billing

The flash storage backed by LUMI-F is billed at a 3x rate compared to the main storage:

TB-hours-billed = 3 x storage-volume x time-used

For example, storing 1.2 TB of data for 4 days consumes:

3 x 1.2 TB x 24 hours/day x 4 days = 345.6 TB-hours

Object storage (LUMI-O) billing

The object storage backed by LUMI-O is billed at a 0.25x rate compared to the main storage:

TB-hours-billed = 0.25 x storage-volume x time-used

For example, storing 1.2 TB of data for 4 days consumes:

0.25 x 1.2 TB x 24 hours/day x 4 days = 28.8 TB-hours

You are viewing a development build

The content on this page has not been approved for release.