Supported virtual machine types

On Azure, WEKA is deployed in a multiple containers architecture using the Lsv3-series of Azure Virtual Machines (Azure VMs), which features high throughput, low latency, and directly mapped local NVMe storage.

Each virtual machine size has a specific number of NICs, but only one is used for UDP mode connection for all traffic through the management interface.

The following table provides the virtual machine sizes that are applied by the Terraform package with their specifications:

VM size	vCPU	Memory (GiB)	NVMe disks	Max NICs	BW (Mbps)
Standard_L8s_v3	8	64	1x1.92 TB	4	12500
Standard_L16s_v3	16	128	2x1.92 TB	8	12500
Standard_L32s_v3	32	256	4x1.92 TB	8	16000
Standard_L48s_v3	48	384	6x1.92 TB	8	24000
Standard_L64s_v3	64	512	8x1.92 TB	8	30000

Note: Using the Azure Console, the client instances can have different virtual machine types provisioned separately from the WEKA cluster.

Related information

Lsv3-series (Azure learning site)

Mapped cores to processes

In each virtual machine size, the cores are mapped to a specific number of the compute, drive, and frontend processes. For example, in the Standard_L16s_v3 size, the cores are mapped to the following processes:

• Compute: 4

• Drive: 2

• Frontend: 1

Mapped WEKA processes for a standard_L16s_v3

VM size	# of compute cores	# of drive cores	# of frontend cores
Standard_L8s_v3	1	1	1
Standard_L16s_v3	4	2	1
Standard_L32s_v3	4	2	1
Standard_L48s_v3	3	3	1
Standard_L64s_v3	4	2	1