6.0.1
Table Of Contents
- vSphere Monitoring and Performance
- Contents
- About vSphere Monitoring and Performance
- Updated Information
- Monitoring Inventory Objects with Performance Charts
- Performance Chart Types
- Data Counters
- Metric Groups in vSphere
- Data Collection Intervals
- Data Collection Levels
- View Performance Charts
- Performance Charts Options Available Under the View Menu
- Overview Performance Charts
- Clusters
- Datacenters
- Datastores
- Disk Space (Data Counters)
- Disk Space (File Types)
- Disk Space (Virtual Machines)
- Storage I/O Control Normalized Latency
- Storage I/O Control Aggregate IOPs
- Storage I/O Control Activity
- Average Device Latency per Host
- Maximum Queue Depth per Host
- Read IOPs per Host
- Write IOPs per Host
- Average Read Latency per Virtual Machine Disk
- Average Write Latency per Virtual Machine Disk
- Read IOPs per Virtual Machine Disk
- Write IOPs per Virtual Machine Disk
- Virtual Machine Observed Latency per Datastore
- Hosts
- Resource Pools
- vApps
- Virtual Machines
- CPU (%)
- CPU Usage (MHz)
- Disk (Average)
- Disk (Rate)
- Disk (Number)
- Virtual Disk Requests (Number)
- Virtual Disk Rate (KBps)
- Memory (Usage)
- Memory (Balloon)
- Memory (Swap Rate)
- Memory (Data Counters)
- Network (Usage)
- Network (Rate)
- Network (Packets)
- Disk Space (Data Counters)
- Disk Space (Datastores)
- Disk Space (File Types)
- Fault Tolerance Performance Counters
- Working with Advanced and Custom Charts
- Troubleshoot and Enhance Performance
- Monitoring Guest Operating System Performance
- Monitoring Host Health Status
- Monitoring Events, Alarms, and Automated Actions
- View Events
- View System Logs
- Export Events Data
- View Triggered Alarms and Alarm Definitions
- Live Refresh of Recent Tasks and Alarms
- Set an Alarm
- Acknowledge Triggered Alarms
- Reset Triggered Event Alarms
- Preconfigured vSphere Alarms
- Monitoring Solutions with the vCenter Solutions Manager
- Monitoring the Health of Services and Nodes
- Performance Monitoring Utilities: resxtop and esxtop
- Using the vimtop Plug-In to Monitor the Resource Usage of Services
- Monitoring Networked Devices with SNMP and vSphere
- Using SNMP Traps with vCenter Server
- Configure SNMP for ESXi
- SNMP Diagnostics
- Monitor Guest Operating Systems with SNMP
- VMware MIB Files
- SNMPv2 Diagnostic Counters
- System Log Files
- Index
Solutions for Consistently High CPU Usage
Temporary spikes in CPU usage indicate that you are making the best use of CPU resources. Consistently
high CPU usage might indicate a problem. You can use the CPU performance charts to monitor CPU usage
for hosts, clusters, resource pools, virtual machines, and vApps.
Problem
n
Host CPU usage constantly is high. A high CPU usage value can lead to increased ready time and
processor queuing of the virtual machines on the host.
n
Virtual machine CPU usage is above 90% and the CPU ready value is above 20%. Application
performance is impacted.
Cause
n
The host probably is lacking the CPU resources required to meet the demand.
n
There might be too many virtual CPUs relative to the number of regular CPUs.
n
There might be an IO storage or networking operation that places the CPU in a wait state.
n
The Guest OS generates too much load for the CPU.
Solution
n
Verify that VMware Tools is installed on every virtual machine on the host.
n
Compare the CPU usage value of a virtual machine with the CPU usage of other virtual machines on
the host or in the resource pool. The stacked bar chart on the host's Virtual Machine view shows the
CPU usage for all virtual machines on the host.
n
Determine whether the high ready time for the virtual machine resulted from its CPU usage time
reaching the CPU limit setting. If so, increase the CPU limit on the virtual machine.
n
Increase the CPU shares to give the virtual machine more opportunities to run. The total ready time on
the host might remain at the same level if the host system is constrained by CPU. If the host ready time
doesn't decrease, set the CPU reservations for high-priority virtual machines to guarantee that they
receive the required CPU cycles.
n
Increase the amount of memory allocated to the virtual machine. This action decreases disk and or
network activity for applications that cache. This might lower disk I/O and reduce the need for the host
to virtualize the hardware. Virtual machines with smaller resource allocations generally accumulate
more CPU ready time.
n
Reduce the number of virtual CPUs on a virtual machine to only the number required to execute the
workload. For example, a single-threaded application on a four-way virtual machine only benefits from
a single vCPU. But the hypervisor's maintenance of the three idle vCPUs takes CPU cycles that could be
used for other work.
n
If the host is not already in a DRS cluster, add it to one. If the host is in a DRS cluster, increase the
number of hosts and migrate one or more virtual machines onto the new host.
n
Upgrade the physical CPUs or cores on the host if necessary.
n
Use the newest version of hypervisor software, and enable CPU-saving features such as TCP
Segmentation Offload, large memory pages, and jumbo frames.
Chapter 1 Monitoring Inventory Objects with Performance Charts
VMware, Inc. 95