Edit

Share via

Performance history for virtual machines

  • Article

Applies to: Windows Server 2022, Windows Server 2019

This sub-topic of Performance history for Storage Spaces Direct describes in detail the performance history collected for virtual machines (VM). Performance history is available for every running, clustered VM.

Note

It may take several minutes for collection to begin for newly created or renamed VMs.

Series names and units

These series are collected for every eligible VM:

Series Unit
vm.cpu.usage percent
vm.memory.assigned bytes
vm.memory.available bytes
vm.memory.maximum bytes
vm.memory.minimum bytes
vm.memory.pressure -
vm.memory.startup bytes
vm.memory.total bytes
vmnetworkadapter.bandwidth.inbound bits per second
vmnetworkadapter.bandwidth.outbound bits per second
vmnetworkadapter.bandwidth.total bits per second

In addition, all virtual hard disk (VHD) series, such as vhd.iops.total, are aggregated for every VHD attached to the VM.

How to interpret

Series Description
vm.cpu.usage Percentage the virtual machine is using of its host server's processor(s).
vm.memory.assigned The quantity of memory assigned to the virtual machine.
vm.memory.available The quantity of memory that remains available, of the amount assigned.
vm.memory.maximum If using dynamic memory, this is the maximum quantity of memory that may be assigned to the virtual machine.
vm.memory.minimum If using dynamic memory, this is the minimum quantity of memory that may be assigned to the virtual machine.
vm.memory.pressure The ratio of memory demanded by the virtual machine over memory allocated to the virtual machine.
vm.memory.startup The quantity of memory required for the virtual machine to start.
vm.memory.total Total memory.
vmnetworkadapter.bandwidth.inbound Rate of data received by the virtual machine across all its virtual network adapters.
vmnetworkadapter.bandwidth.outbound Rate of data sent by the virtual machine across all its virtual network adapters.
vmnetworkadapter.bandwidth.total Total rate of data received or sent by the virtual machine across all its virtual network adapters.

Note

Counters are measured over the entire interval, not sampled. For example, if the VM is idle for 9 seconds but spikes to use 50% of host CPU in the 10th second, its vm.cpu.usage will be recorded as 5% on average during this 10-second interval. This ensures its performance history captures all activity and is robust to noise.

Usage in PowerShell

Use the Get-VM cmdlet:

Get-VM <Name> | Get-ClusterPerf

Note

The Get-VM cmdlet only returns virtual machines on the local (or specified) server, not across the cluster.

Additional References