Capacity Monitoring
ZSvirt provides information on the usage and allocation of various computing and storage resources, including virtual machines, hosts, clusters, data storage, data centers, and root nodes (management nodes). This allows you to comprehensively understand the platform's resource usage from both micro and macro perspectives.
Capacity Monitoring Metrics
You can go to the overview details page of the corresponding resource to understand the platform's resource usage from the Capacity Information card. The following table lists the detailed monitoring metrics for various resources.
Object | Monitoring Metrics and Description |
|---|---|
Root Node |
|
Data Center |
|
Data Storage |
|
Cluster |
|
Host |
|
Virtual Machine |
|
Capacity Calculation Rules
Category | Calculation Rules |
|---|---|
Resource Utilization Rate | Total CPU = Physical Cores × Single-Core GHz |
Resource Allocation Ratio |
|
Resource Distribution | CPU- CPU Overcommitted Total = Physical CPU Total × Overcommit Ratio Memory- Memory Overcommitted Total = Reserved Memory + Total Allocatable Memory Capacity
Storage- Storage Overcommitted Total = Reserved Capacity + Total Allocatable Storage Capacity
|
The meaning of overcommitment and allocation are as follows:
-
CPU Overcommitment: This indicates that a single physical CPU core can be virtually divided into N logical CPU cores for allocation to virtual machines.
For example, if the CPU overcommitment ratio is 2:1, then one physical CPU core can be virtually divided into 2 logical CPU cores. Therefore, if a host has 10 physical CPU cores, it can be virtually divided into 20 logical CPU cores for allocation to virtual machines.
-
Memory/Storage Overcommitment: This indicates that a unit of memory/storage capacity can be virtually expanded into N units of memory/storage capacity for allocation to virtual machines.
For example, if the memory/storage overcommitment ratio is 2:1, then 1 GB of memory/storage capacity can be virtually expanded into 2 GB. Therefore, if a host has 100 GB of memory/storage, it can be virtually expanded into 200 GB for allocation to virtual machines.
-
CPU Allocation: This indicates that a physical CPU core is actually virtually divided into N logical CPU cores for use by virtual machines. Therefore, the CPU allocation ratio ≤ CPU overcommitment ratio.
For example, if the CPU allocation ratio is 1.5:1, then one physical CPU core is actually virtually divided into 1.5 logical CPU cores. Therefore, if a host has 10 physical CPU cores, they have actually been virtually divided into 15 logical CPU cores for allocation to virtual machines.
-
Memory/Storage Allocation: This indicates that a unit of memory/storage capacity is actually virtually expanded into N units of memory/storage capacity. Therefore, the memory/storage allocation ratio ≤ memory/storage overcommitment ratio.
For example, if the memory/storage overcommitment ratio is 1.5:1, then 1 GB of memory/storage capacity is actually virtually expanded into 1.5 GB. Therefore, if a host has 100 GB of memory/storage, it has actually been virtually expanded into 150 GB for allocation to virtual machines.
Using host storage as an example, if the total physical storage capacity is 100 GB, the reserved physical capacity is 10 GB, the overcommitment ratio is 2:1, and the allocated capacity is 150 GB, then:
- Storage Allocation Ratio = 150 GB : 90 GB = 1.67
- Total Overcommit Storage = 100 GB - 10 GB = 90 GB
- Total Allocatable Storage = 90 GB × 2 = 180 GB
- Remaining Allocatable Storage = 180 GB - 150 GB = 30 GB