SLURM Charges
Billing Rates
Note there may be different versions of a resource type, each having different performance characteristics. For example, a CPU job might end up being run on a Sandy Bridge, Haswell, or SkyLake CPU, which are different-generation processors and have different processing speeds. SLURM is aware of the different versions of a resource and will charge appropriately. At present, the relative performance charges are:
CPU and GPU Billing Rates
Resource Type | Resource Version | SUs Charged Per Core Per Hour |
---|---|---|
CPU | Skylake | 1 |
CPU | Cascade Lake | 1 |
CPU | AMD Rome | 1 |
CPU | Icelake Lake | 1 |
VM | Skylake vCPU | 1 |
GPU | P100 | 1 |
GPU | V100 | 1.48 |
GPU | A100 | 2.1 |
Note that the Sandy Bridge and Haswell CPUs are only used in the DLX 2 nodes. Because the DLX 2 nodes are available at no cost to users, their SU charge per core per hour is 0 SUs.
Performance Ratios
The following table shows the relative performance of the various processors
that are part of the LCC system (using Sandy Bridge and P100s as the base performance).
CPU and GPU Performance Ratios
Resource Type | Resource Version | Relative Performance |
---|---|---|
CPU | Sandy Bridge | 1 |
CPU | Haswell | 1.59 |
CPU | Skylake | 2.91 |
CPU | Cascade Lake | 2.91 |
CPU | AMD Rome | 1.38 |
CPU | Ice Lake | 2.77 |
VM | Sandy Bridge vCPU | 1 |
VM | Haswell vCPU | 1.59 |
VM | Skylake vCPU | 2.91 |
VM | AMD Rome vCPU | 1.38 |
VM | Icelake vCPU | 2.77 |
GPU | P100 | 1 |
GPU | V100 | 1.48 |
GPU | A100 | 2.1 |
Â
Center for Computational Sciences