Below an example and some guiidelines/tips on interpretation of perfoemance analysis using ESXTOP. ID GID NAME NWLD %USED %RUN %SYS %WAIT %VMWAIT%RDY %ID 1 1 idle 2 3116 3116 XP2Lite1_iSCSI 7 352430 352430 esxtop.220681 1 1 / 9
8 8 helper 80 346060 346060 hostd.216824 13 346720 346720 vpxa.217252 19 2 / 9
Default the screen will be refreshed every 5 seconds, change this by typing: s 2 Changing views is easy type the following keys for the associated views: c = cpu m = memory n = network i = interrupts d = disk adapter u = disk device (includes NFS as of 4.0 Update 2) v = disk VM p = power states V = only show virtual machine worlds e = Expand/Rollup CPU statistics, show details of all worlds associated with group (GID) k = kill world, for tech support purposes only! l = limit display to a single group (GID), enables you to focus on one VM # = limiting the number of entitites, for instance the top 5 2 = highlight a row, moving down 8 = highlight a row, moving up 4 = remove selected row from view e = statistics broken down per world 6 = statistics broken down per world ESXTop Metrics and Thresholds Display Metric Th% Explanation CPU %RDY 10 Overprovisioning of vcpus, excessive usage of vsmp or a limit(check % 3 / 9
CPU %CSTP 3 Excessive usage of vsmp. Decrease amount of vcpus for this particula CPU %SYS 20 The percentage of time spent by system services on behalf of the world CPU %MLMTD 0 The percentage of time the vcpu was ready to run but deliberately was CPU %SWPWT 5 VM waiting on swapped pages to be read from disk. Possible cause: Me MEM MCTLSZ 1 If larger than 0 host is forcing VMs to inflate balloon driver to reclaim me MEM SWCUR 1 If larger than 0 host has swapped memory pages in the past. Possible c MEM SWR/s 1 If larger than 0 host is actively reading from swap(vswp). Possible cause MEM SWW/s 1 If larger than 0 host is actively writing to swap(vswp). Possible cause: E MEM CACHEUSD0 If larger than 0 host has compressed memory. Possible cause: Memory MEM ZIP/s 0 If larger than 0 host is actively compressing memory. Possible cause: M 4 / 9
MEM UNZIP/s 0 If larger than 0 host has accessing compressed memory. Possible caus MEM N%L 80 If less than 80 VM experiences poor NUMA locality. If a VM has a memo NETWORK %DRPTX 1 Dropped packets transmitted, hardware overworked. Possible cause: ve NETWORK %DRPRX 1 Dropped packets received, hardware overworked. Possible cause: very DISK GAVG 25 Look at DAVG and KAVG as the sum of both is GAVG. DISK DAVG 25 Disk latency most likely to be caused by array. DISK KAVG 2 Disk latency caused by the VMkernel, high KAVG usually means queuin DISK QUED 1 Queue maxed out. Possibly queue depth set to low. Check with array ve DISK ABRTS/s 1 Aborts issued by guest(vm) because storage is not responding. For Win 5 / 9
DISK RESETS/s 1 The number of commands reset per second. DISK CONS/s 20 SCSI Reservation Conflicts per second. If many SCSI Reservation Conf Copied from http://www.yellow-bricks.com/esxtop/ and slightly modified for use at POCS. y default the screen will be refreshed every 5 seconds, change this by typing: 6 / 9
s 2 Changing views is easy type the following keys for the associated views: c = cpu m = memory n = network i = interrupts 7 / 9
d = disk adapter u = disk device (includes NFS as of 4.0 Update 2) v = disk VM p = power states V = only show virtual machine worlds e = Expand/Rollup CPU statistics, show details of all worlds associated with group (GID) k = kill world, for tech support purposes only! 8 / 9
l = limit display to a single group (GID), enables you to focus on one VM # = limiting the number of entitites, for instance the top 5 2 = highlight a row, moving down 8 = highlight a row, moving up 4 = remove selected row from view e = statistics broken down per world 6 = statistics broken down per world 9 / 9