3.1 Virtual machine flavors and Billing Unit rates

The cPouta and ePouta services consume the same billing units as Sisu and Taito. You can find more information in the CSC Computing environment user guide.

Users can create virtual machines with larger compute resources or smaller resources based upon their needs. The Virtual Machine flavors available in cPouta are listed in Table 3.1 and the flavors available in ePouta in Table 3.2.

Table 3.1 Available virtual machine  flavors in cPouta and their Billing Unit coefficients. Note that the default  cPouta  user account allows users to launch only a subset of the available virtual machine  flavors . 

cPouta Flavors
Standard flavors
Flavor Cores Memory
(* GiB)
Disk (root) Disk (ephemeral) Disk (total) Memory/core
(* GiB)
Billing Units/h
standard.tiny 1 1 80 GB 0 GB 80 GB 1 0.5
standard.small 2 2 80 GB 0 GB 80 GB 1 1
standard.medium 3 4 80 GB 0 GB 80 GB 1.3 2
standard.large 4 8 80 GB 0 GB 80 GB 2 4
standard.xlarge 6 16 80 GB 0 GB 80 GB 2.6 8
standard.xxlarge 8 32 80 GB 0 GB 80 GB 4 12
HPC flavors
Flavor Cores Memory
(* GiB)
Disk (root) Disk (ephemeral) Disk (total) Memory/core
(* GiB)
Billing Units/h
hpc.4.5core 5 22 80 GB 0 GB 80 GB 4.3 10
hpc.4.10core 10 43 80 GB 0 GB 80 GB 4.3 20
hpc.4.20core 20 86 80 GB 0 GB 80 GB 4.3 40
hpc-gen2.24core 24 120 80 GB (RAID0) 0 GB 80 GB 5 45
hpc-gen2.48core 48 240 80 GB (RAID0) 0 GB 80 GB 5 90
I/O flavors
Flavor Cores Memory
(* GiB)
Disk (root) Disk (ephemeral) Disk (total) Memory/core
(* GiB)
Billing Units/h
io.70GB 2 10 20 GB
(SSD/RAID0)
70 GB
(SSD/RAID0)
90 GB 5 5
io.160GB 4 20 20 GB
(SSD/RAID0)
160 GB
(SSD/RAID0)
180 GB 5 10
io.340GB 8 40 20 GB
(SSD/RAID0)
340 GB
(SSD/RAID0)
360 GB 5 20
io.700GB 16 80 20 GB
(SSD/RAID0)
700 GB
(SSD/RAID0)
720 GB 5 40
GPU flavors
Flavor Cores GPUs Memory
(* GiB)
Disk (root) Disk (total) Memory/core
(* GiB)
Billing Units/h
gpu.1.1gpu 14 1 120 80 GB (SSD/RAID1) 80 GB 8.5 60
gpu.1.2gpu 28 2 240 80 GB (SSD/RAID1) 80 GB 8.5 120
gpu.1.4gpu 56 4 480 80 GB (SSD/RAID1) 80 GB 8.5 240
Deprecated flavors
Flavor Cores Memory
(* GiB)
Disk (root) Disk (ephemeral) Disk (total) Memory/core
(* GiB)
Billing Units/h
hpc-gen1.1core 1 3.7 80 GB (RAID0) 0 GB 80 GB 3.7 2
hpc-gen1.4core 4 15 80 GB (RAID0) 0 GB 80 GB 3.7 8
hpc-gen1.8core 8 30 80 GB (RAID0) 0 GB 80 GB 3.7 16
hpc-gen1.16core 16 60 80 GB (RAID0) 0 GB 80 GB 3.7 32
hpc-gen2.2core 2 10 80 GB (RAID0) 0 GB 80 GB 5 4
hpc-gen2.8core 8 40 80 GB (RAID0) 0 GB 80 GB 5 15
hpc-gen2.16core 16 80 80 GB (RAID0) 0 GB 80 GB 5 30
tiny 1 1 10 GB (RAID0) 110 GB (RAID0) 120 GB 1 2
mini 1 3.5 10 GB (RAID0) 110 GB (RAID0) 120 GB 1.7 2
small 4 15 10 GB (RAID0) 220 GB (RAID0) 230 GB 3.8 8
medium 8 30 10 GB (RAID0) 440 GB (RAID0) 450 GB 3.8 16
large 12 45 10 GB (RAID0) 660 GB (RAID0) 670 GB 3.8 24
fullnode 16 60 10 GB (RAID0) 900 GB (RAID0) 910 GB 3.8 32


* Not all memory amounts round exactly to GiB, the closest value has been used.

Table 3.2 Available virtual machine flavors in ePouta and their Billing Unit coefficients.

ePouta Flavors
Standard flavors
Flavor Cores Memory
(* GiB)
Disk (root) Disk (ephemeral) Disk (total) Memory/core
(* GiB)
Billing Units/h
standard.tiny 1 1 80 GB 0 GB 80 GB 1 0.5
standard.small 2 2 80 GB 0 GB 80 GB 1 1
standard.medium 3 4 80 GB 0 GB 80 GB 1.3 2
standard.large 4 8 80 GB 0 GB 80 GB 2 4
standard.xlarge 6 16 80 GB 0 GB 80 GB 2.6 8
HPC flavors
Flavor Cores Memory
(* GiB)
Disk (root) Disk (ephemeral) Disk (total) Memory/core
(* GiB)
Billing Units/h
hpc.fullnode.haswell 46 242 80 GB 0 GB 80 GB 5.4 120
hpc.3.28core 28 120 80 GB 0 GB 80 GB 4.4 70
hpc.3.56core 56 240 80 GB 0 GB 80 GB 4.4 140
hpc.4.10core 10 45 80 GB 0 GB 80 GB 4.5 23
hpc.4.20core 20 90 80 GB 0 GB 80 GB 4.4 45
hpc.4.40core 40 180 80 GB 0 GB 80 GB 4.4 90
hpc.4.80core 80 360 80 GB 0 GB 80 GB 4.4 180
I/O flavors
Flavor Cores Memory
(* GiB)
Disk (root) Disk (ephemeral) Disk (total) Memory/core
(* GiB)
Billing Units/h
io.haswell.2core 2 10 20 GB
(SSD/RAID0)
70 GB
(SSD/RAID0)
90 GB 5 7
io.haswell.4core 4 20 20 GB
(SSD/RAID0)
160 GB
(SSD/RAID0)
180 GB 5 13
io.haswell.8core 8 40 20 GB
(SSD/RAID0)
350 GB
(SSD/RAID0)
370 GB 5 25
io.haswell.16core 16 80 20 GB
(SSD/RAID0)
700 GB
(SSD/RAID0)
720 GB 5 50
io.haswell.32core 32 160 20 GB
(SSD/RAID0)
1400 GB
(SSD/RAID0)
1420 GB 5 100
io.haswell.46core 46 242 20 GB
(SSD/RAID0)
2100 GB
(SSD/RAID0)
2120 GB 5.4 150
High Memory flavors
Flavor Cores

Memory
(* GiB)

Disk (root) Disk (ephemeral) Disk (total)

Memory/core
(* GiB)

Billing Units/h
tb.westmere.32core 32 488 80 GB
(RAID6)
3250 GB
(RAID6)
3330 GB 15.2 200
tb.westmere.64core 64 976 80 GB
(RAID6)
6500 GB
(RAID6)
6580 GB 15.2 400
tb.3.480RAM 56 480 80 GB
(SSD/RAID0)
1650 GB
(NVMe/RAID0)
1730 GB 8.5 200
tb.3.1470RAM 80 1470 80 GB
(SSD/RAID0)
2500 GB
(NVMe/RAID0)
2580 GB 18.3 600
tb.4.735RAM 80 735 80 GB
(SSD/RAID0)
1250 GB
(SSD/RAID0)
1330 GB 9.2 350
GPU flavors (only available via request to servicedesk)
Flavor Cores

Memory
(* GiB)

Disk (root) Disk (ephemeral) Disk (total)

Memory/core
(* GiB)

Billing Units/h
gpu.2.1gpu 20 180 80 GB
(SSD/RAID0)
1000 GB
(SSD/RAID0)
1080 GB 9 140
Deprecated flavors
Flavor Cores

Memory
(* GiB)

Disk (root) Disk (ephemeral) Disk (total)

Memory/core
(* GiB)

Billing Units/h
hpc.mini 2 3.5 80 GB 0 GB 80 GB 1.8 5
hpc.small 4 7 80 GB 0 GB 80 GB 1.8 10
hpc.medium.haswell 8 40 80 GB 0 GB 80 GB 5 20
hpc.large.haswell 16 80 80 GB 0 GB 80 GB 5 40
hpc.xlarge.haswell 32 156 80 GB 0 GB 80 GB 5 80
hpc.medium.westmere 8 14 80 GB 0 GB 80 GB 1.8 8
hpc.large.westmere 16 28 80 GB 0 GB 80 GB 1.8 16
hpc.xlarge.westmere 23 41 80 GB 0 GB 80 GB 1.8 24

hpc.largemem.westmere
23 90 80 GB 0 GB 80 GB 4 36


* Not all memory amounts round exactly to GiB, the closest value has been used.

Please note: Table 3.2 has flavors that are slightly different then the cPouta flavors listed in Table 3.1. This is because different hardware is used in these two clouds. Any storage with a comment in parenthesis such as (SSD/RAID0) means that particular storage is local to the compute node. In ePouta, the HPC root disks and standalone volumes are hosted in the centralized Ceph block storage system.

Which type of flavor should I use?

Standard flavors

Typical use cases:

  • Web services (non-HPC)
  • Software development

These are generic flavors that are useful for running regular web services like a web server with a database backend or some other relatively light usage. They provide better availability compared to HPC flavors.

Cloud administrators can move these virtual machines from one host machine to another without causing a break in service. This means that you are likely less impacted by maintenance.

These flavors are not suitable for computationally intensive workloads. The virtual CPUs used in these instances are overcommitted, which means 32 hyperthreaded CPU cores are used to provide more than 32 virtual cores.

 Flavor characteristics:

  • Redundant power
  • CPU: Varies
  • Network: Redundant 25 Gb/s
  • Flavor disk: Stored on central storage
  • Single node or disk failures may cause downtime, but your instance is recoverable.

HPC flavors

Typical use cases:

  • Scientific applications

If your use case is computationally intensive, you should use one of the HPC flavors. The availability for these instances is not as high as with the standard flavors, but you get better performance. The HPC flavors have faster CPUs and no overcommitment of CPU cores.

cPouta HPC flavor characteristics:

hpc.4.*:

  • Not redundant power
  • CPU: Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz, hyper-threading
  • Network: Redundant 25 Gb/s
  • Flavor disk: Stored on central storage
  • Single node or disk failures may cause downtime, but your instance is recoverable.

hpc-gen2.*:

  • No redundant power
  • CPU: Intel(R) Xeon(R) CPU E5-2680 v3, with hyper-threading
  • Network: Single 40 Gb/s
  • Flavor disk: Local SATA disk, no RAID
  • Your instance can be lost due to a single node or disk failure.

ePouta HPC flavor characteristics:

hpc.4*:

  • Redundant power
  • CPU: Intel(R) Xeon(R) CPU Gold 6148, with hyper-threading
  • Network: Redundant 25 Gb/s
  • Flavor disk: Stored on central storage
  • Single node or disk failures may cause downtime, but your instance is recoverable.

hpc.3*:

  • Redundant power
  • CPU: Intel(R) Xeon(R) CPU E5-2680 v4, with hyper-threading
  • Network: Redundant 25 Gb/s
  • Flavor disk: Stored on central storage
  • Single node or disk failures may cause downtime, but your instance is recoverable.

hpc.*.haswell:

  • Redundant power
  • CPU: Intel(R) Xeon(R) CPU E5-2690 v3, with hyper-threading
  • Network: Redundant 10 Gb/s
  • Flavor disk: Stored on central storage
  • Single node or disk failures may cause downtime, but your instance is recoverable.

I/O flavors

Typical use cases:

  • Hadoop/Spark
  • Non-critical centralized databases
  • Clustered databases

I/O flavors are intetended to give you the best I/O performance on the virtual machine root and ephemeral disks. They are backed by local SSDs on the servers they run on. The SSDs are configured in a RAID-0 configuration for maximal performance. This means there is an increased risk of loss of a virtual machine in case of hardware problems. The risk of disk failure is larger than on the other flavors, so it's especially important to be aware of the risks of data-loss on these flavors.

As these instances are also tightly tied to the hardware, you may expect downtime of instances during maintenance of the hardware. Resize/migration functionality also does not work for these instances. The bulk of the storage is available as an ephemeral disk, normally under /dev/vdb.

Often you want to create clusters of servers with the io.* flavors. In these cases you probably want to have your virtual machines land on different physical servers. This can not currently be done in the web interface. To achieve this, please refer to the anti-affinity group commands in our command line instructions.

The availability for these instances is not as high as with the standard flavors, but you get significantly better I/O performance. Maintenance work can cause larger disruption, and the resize functionality does not work.

cPouta IO flavor characteristics:

io.*:

  • Redundant power
  • CPU: Intel(R) Xeon(R) CPU E5-2680 v3, with hyper-threading
  • Network: Redundant 10 Gb/s or 40 Gb/s
  • Flavor disk: Local SSD disks, RAID-0
  • Your instance can be lost due to a single node or disk failure.

ePouta IO flavor characteristics:

io.haswell.*:

  • Redundant power
  • CPU: Intel(R) Xeon(R) CPU E5-2680 v3, with hyper-threading
  • Network: Redundant 10 Gb/s
  • Flavor disk: Local SSD disks, RAID-0
  • Your instance can be lost due to a single node or disk failure.

GPU Flavors

Typical Usecases:

  • High Performance Compute applications leveraging GPUs
  • Machine and deep learning for ex. TensorFlow
  • Rendering

GPU flavors are intended to give you high performance computing using GPGPU (General Purpose computing on Graphical Processing Units). GPGPUs can significantly speed up some algorithms and applications. The gpu.1. flavors in cPouta have NVIDIA Tesla P100 GPGPUs. The gpu.2.1gpu in ePouta have NVIDIA Tesla V100 GPGPU

The GPGPUs are suitable for deep learning, scientific computing as well as for remote desktop, rendering or visualization. The GPGPU flavors are backed by local SSD on the servers. The SSD in cPouta are configured in RAID-1 and this is where the OS root disk is stored. In ePouta the SSD are bigger than in cPouta and the SSDs are configured in RAID-0 for faster staging of datasets. You can use the volumes for storing larger data sets. If you need to read and write a lot of data between the disk and GPGPU, this might affect the performance.

To take advantage of the acceleration which GPGPUs provide, the applications you run must have support for using them. If you write your own applications, the Optimization Service can offer help in leveraging the GPGPUs.

We know GPGPUs can be used for a lot of cool and interesting things, but please remember the resource usage must comply with the Terms of Use.

Limitations & caveats: 

  • As we use PCI passthrough to get the whole GPGPU into the instance, the administrators are not able to access the GPGPU and check its health. Please report errors or problems with the GPGPUs to CSC (and attach the output of the command "nvidia-smi -q" when you do so).
  • Applications must be able to utilize the GPU to get a speedup.

These instances are also tightly tied to the hardware, you may expect downtime of instances during maintenance of the hardware. The NVIDIA Tesla V100 GPGPU are also available in the batch system on Taito: https://research.csc.fi/taito-gpu.

cPouta flavor characteristics:

gpu.1.*:

  • Redundant power
  • CPU: Intel(R) Xeon(R) CPU E5-2680 v4, with hyper-threading
  • Network: Redundant 10 Gb/s
  • Flavor disk: Local SSD disks, RAID-1
  • Your instance can be lost due to a single node or disk failure.

ePouta flavor characteristics:

gpu.2.*:

  • Only available via request to servicedesk@csc.fi
  • Redundant power
  • CPU: Intel(R) Xeon(R) Gold 6148, with hyper-threading
  • NUMA Aware: yes (CPU <> Memory, not PCI devices)
  • Network: Redundant 10 Gb/s
  • Flavor disk: Local SSD disks, RAID-0
  • Your instance can be lost due to a single node or disk failure.

Installation and configuration of GPU Flavors

We have specific CUDA images available for use with the GPU nodes. These images come pre-installed with the freshest CUDA version. Note that the CUDA images are not configure with auto update. One may use any other images with the GPU flavors, but in this case, you will have to install the required libraries yourself. If you want to use your own images, https://research.csc.fi/pouta-adding-images has more details about how CSC customizes the images.

High Memory Flavors (only in ePouta)

Typical use cases:

  • Scientific applications requiring large amounts of memory

These flavors have large amount of memory, and are meant for use cases which require, and can utilize this amount of memory. Typical usecases of these flavors include scientific applications with huge memory requirements for example Gnome sequencing and analysis applications etc.

Flavor characteristics:

tb.westmere.*:

  • Redundant power
  • CPU: Intel(R) Xeon(R) CPU E5-4620, with hyper-threading
  • Network: Redundant 10 Gb/s
  • Flavor disk: Local SAS RAID-5
  • Your instance can be lost due to a single node failure. Single disk failures should not affect your instance.

tb.3.*:

  • Redundant power
  • CPU: Intel(R) Xeon(R) CPU E5-2680 v4, with hyper-threading or Intel(R) Xeon(R) CPU E5-2698 v4, with hyper-threading
  • Network: Redundant 25 Gb/s
  • Flavor disk: Local SSD disks, RAID-0
  • Your instance can be lost due to a single node or disk failure.

tb.4.*:

  • Redundant power
  • CPU: Intel(R) Xeon(R) CPU Gold 6148, with hyper-threading
  • Network: Redundant 25 Gb/s
  • Flavor disk: Local SSD disks, RAID-0
  • Your instance can be lost due to a single node or disk failure.

Deprecated flavors

This is the set of original flavors that has been available since launch. You should not launch any new virtual machines using any of these flavors. Existing virtual machines that use these flavors will continue to work. We will maintain these flavors for a period of time, but they will be removed at some point in the near future.

 
Previous chapter   One level up   Next chapter