Virtual machines (VMs) require certain CPU core resources and have and other limits for memory, networks, and storage.
The number of cores recommended for everRun workloads depends upon the number of vCPUs in each VM and the types of the VMs as described below:
Item | Number of Physical Threads |
---|---|
Fixed system overhead (host and system management) | 2 |
Each FT guest with n vCPUs | n + 2 (typical) |
Each HA guest with n vCPUs | n + 1 (typical) |
The actual number of required threads depends upon the workload. The guidelines above should cover most workloads. Since any given workload may require fewer or more threads, it’s good practice to test and characterize your specific workload.
Examples
A single 4-vCPU FT guest typically requires:
2 threads for host/system management
6 threads for guest
8 threads total (a single socket 4-core hyper-threaded system)
Four 5-vCPU FT guests typically require:
2 threads for host/system management
7 threads for first guest
7 threads for second guest
7 threads for third guest
7 threads for fourth guest
30 threads total (a dual socket 8-core hyper-threaded system)
For systems with many or large virtual machines (VMs), configure everRun with 10 Gb sync links, and for the everRun software itself, 4 vCPUs and 4096 MB. Refer to the Preferences -> Systems Resources page in the everRun Availability Console for instructions on setting the everRun system resources to the maximum.
The following table lists everRun system VM limits.
Item |
Limits |
---|---|
Maximum VCPUs per FT VM |
|
Maximum VCPUs per HA VM |
|
Maximum Memory per FT VM |
|
Maximum Memory per HA VM |
|
Maximum Availability Links per VM |
2 |
Maximum Virtual Networks per VM | 20 |
Maximum Storage Volumes per VM |
12 |
|
|
Max. Snapshots per VM | 16 (72 total per system) |
Product Support and Downloads
|
About Stratus
|
Product Documentation (PDF Format)
|
About Help
|