The vCores and RAM you specify in this tool translate directly to resource requests and limits in Kubernetes, which is the underlying platform for Azure Arc Data Services.

CPU (vCores)

CPU resources are measured in Kubernetes CPU units. One vCore in this tool is equivalent to one Kubernetes CPU unit. This can also be expressed as 1000m (millicores or millicpu). For example, specifying 2 vCores for a service sets its Kubernetes CPU request to '2' or '2000m'. Kubernetes uses this value to guarantee that the service gets the requested CPU power.

Memory (RAM)

Memory is measured in bytes. Kubernetes understands units like Gi (Gibibytes) and Mi (Mebibytes). This tool simplifies it to GB (Gigabytes) for ease of use. When you enter 4 GB of RAM, it sets the Kubernetes memory request to a value like '4Gi', ensuring the service has that much memory reserved for it.

Key takeaway: The values you enter are used to define the minimum guaranteed resources (requests) for each component in your Kubernetes cluster, ensuring stable performance.

This example demonstrates a common deployment scenario. Click the button below to load these values into the tool and see the calculation in action.

• Data Controller: 4 vCores, 4 GB RAM
• SQL MI (General Purpose): 1 instance with 2 vCores, 4 GB RAM
• SQL MI (Business Critical): 1 instance with 4 vCores, 8 GB RAM (resources are x3 for replicas)
• PostgreSQL Hyperscale: 1 group with 2 workers, each node (coordinator + workers) having 2 vCores, 4 GB RAM

Breakdown:

• Data Controller: 4 vCores, 4 GB RAM
• SQL MI (GP) Total: 2 vCores, 4 GB RAM
• SQL MI (BC) Total: (4 vCores * 3 replicas) = 12 vCores, (8 GB RAM * 3 replicas) = 24 GB RAM
• PostgreSQL Total: (1 coordinator + 2 workers) * 2 vCores = 6 vCores, (1 coordinator + 2 workers) * 4 GB RAM = 12 GB RAM

Example Total: 24 vCores and 44 GB RAM required across the cluster.