ESXTOP Metrics Review

Question 1

%USED

Answer 1

CPU use. The percentage of physical CPU core cycles used by a group of worlds running VMs, resource pools, or other worlds

Question 2

%RDY:

Answer 2

Percentage of time that the VM was ready to run but was not provided CPU resources on which to execute.

Question 3

%CSTP:

Answer 3

Percentage of time that the vCPUs of a VM spent in the co-stop state, waiting to be co-started. This value gives an indication of the co-scheduling overhead incurred by the VM. If this value is low, any performance problems should be attributed to other issues and not to the co-scheduling of the VM’s vCPUs.

Question 4

%MLMTD:

Answer 4

Percentage of time that the VMkernel did not run the VM because that would violate the VM’s limit setting.

Question 5

%VMWAIT:

Answer 5

Percentage of time that the VM spent in a blocked state waiting for events.

Question 6

%SWPWT:

Answer 6

Percentage of time that the VM spends waiting for the VMkernel to swap memory.

Question 7

NWLD:

Answer 7

Number of members in the VM of the world that is running.

Question 8

MbTX/s:

Answer 8

Amount of data transmitted (in megabits) per second

Question 9

MbRX/s:

Answer 9

Amount of data received (in megabits) per second

Question 10

PKTTX/s:

Answer 10

Average number of packets transmitted per second in the sampling interval

Question 11

PKTRX/s:

Answer 11

Average number of packets received per second in the sampling interval

Question 12

%DRPTX:

Answer 12

Percentage of outbound packets dropped in the sampling interval

Question 13

%DRPRX:

Answer 13

Percentage of inbound packets dropped in the sampling interval

Question 14

ESXTOP

PMEM:

Answer 14

The total amount of physical memory on your host in megabytes.

Question 15

ESXTOP

VMKMEM:

Answer 15

The memory that is managed by the VMkernel in megabytes.

Question 16

ESXTOP

PSHARE:

Answer 16

The saving field shows you how much memory you saved because of TPS.

Question 17

ESXTOP

Memory state:

Answer 17

This value can be high, clear, soft, hard, or low. This value refers to the current state of the VMkernel’s memory. This value also indicates whether the VMkernel has enough free memory to perform its critical operations.

Question 18

ESXTOP

MEMCTL/MB:

Answer 18

This line displays the memory balloon statistics for the entire host.

Question 19

ESXTOP

MCTL?:

Answer 19

This value, which is either Y (for yes) or N (for no), indicates whether the balloon driver is installed in the VM.

Question 20

ESXTOP

MCTLSZ:

Answer 20

This value is reported for each VM and represents the amount of physical memory that the balloon driver is holding for use by other VMs.

Question 21

ESXTOP

MCTLTGT:

Answer 21

This value is the amount of physical memory that the host wants to reclaim from the VM through ballooning.

Question 22

ESXTOP

CACHESZ (MB):

Answer 22

Compression memory cache size

Question 23

ESXTOP

CACHEUSD (MB):

Answer 23

Used compression memory cache

Question 24

ESXTOP

ZIP/s (MB/s):

Answer 24

Compressed memory per second

Question 25

ESXTOP UNZIP/s (MB/s):

Answer 25

Decompressed memory per second

Question 26

ESXTOP LLSWR/s

Answer 26

is the rate (in MB) at which memory is read from the host cache.

Question 27

ESXTOP LLSWW/s

Answer 27

is the rate (in MB) at which memory is written to the host cache.

Question 28

ESXTOP SWR/s and SWW/s:

Answer 28

Measured in megabytes, these counters represent the rate at which the ESXi host is swapping memory in from disk (SWR/s) and swapping memory out to disk (SWW/s).

Question 29

ESXTOP SWCUR:

Answer 29

The amount of swap space currently used by the VM.

Question 30

ESXTOP SWTGT:

Answer 30

The amount of swap space that the host expects the VM to use.

Question 32

CPU use. The percentage of physical CPU core cycles used by a group of worlds running VMs, resource pools, or other worlds

Answer 32

%USED

Question 33

Percentage of time that the VM was ready to run but was not provided CPU resources on which to execute.

Answer 33

%RDY:

Question 34

Percentage of time that the vCPUs of a VM spent in the co-stop state, waiting to be co-started. This value gives an indication of the co-scheduling overhead incurred by the VM. If this value is low, any performance problems should be attributed to other issues and not to the co-scheduling of the VM’s vCPUs.

Answer 34

%CSTP:

Question 35

Percentage of time that the VMkernel did not run the VM because that would violate the VM’s limit setting.

Answer 35

%MLMTD:

Question 36

Percentage of time that the VM spent in a blocked state waiting for events.

Answer 36

%VMWAIT:

Question 37

Percentage of time that the VM spends waiting for the VMkernel to swap memory.

Answer 37

%SWPWT:

Question 38

Number of members in the VM of the world that is running.

Answer 38

NWLD:

Question 39

Amount of data transmitted (in megabits) per second

Answer 39

MbTX/s:

Question 40

Amount of data received (in megabits) per second

Answer 40

MbRX/s:

Question 41

Average number of packets transmitted per second in the sampling interval

Answer 41

PKTTX/s:

Question 42

Average number of packets received per second in the sampling interval

Answer 42

PKTRX/s:

Question 43

Percentage of outbound packets dropped in the sampling interval

Answer 43

%DRPTX:

Question 44

Percentage of inbound packets dropped in the sampling interval

Answer 44

%DRPRX:

Question 45

The total amount of physical memory on your host in megabytes.

Answer 45

ESXTOP PMEM:

Question 46

The memory that is managed by the VMkernel in megabytes.

Answer 46

ESXTOP VMKMEM:

Question 47

The saving field shows you how much memory you saved because of TPS.

Answer 47

ESXTOP PSHARE:

Question 48

This value can be high, clear, soft, hard, or low. This value refers to the current state of the VMkernel’s memory. This value also indicates whether the VMkernel has enough free memory to perform its critical operations.

Answer 48

ESXTOP Memory state:

Question 49

This line displays the memory balloon statistics for the entire host.

Answer 49

ESXTOP MEMCTL/MB:

Question 50

This value, which is either Y (for yes) or N (for no), indicates whether the balloon driver is installed in the VM.

Answer 50

ESXTOP MCTL?:

Question 51

This value is reported for each VM and represents the amount of physical memory that the balloon driver is holding for use by other VMs.

Answer 51

ESXTOP MCTLSZ:

Question 52

This value is the amount of physical memory that the host wants to reclaim from the VM through ballooning.

Answer 52

ESXTOP MCTLTGT:

Question 53

Compression memory cache size

Answer 53

ESXTOP CACHESZ (MB):

Question 54

Used compression memory cache

Answer 54

ESXTOP CACHEUSD (MB):

Question 55

Compressed memory per second

Answer 55

ESXTOP ZIP/s (MB/s):

Question 56

Decompressed memory per second

Answer 56

ESXTOP UNZIP/s (MB/s):

Question 57

is the rate (in MB) at which memory is read from the host cache.

Answer 57

ESXTOP LLSWR/s

Question 58

is the rate (in MB) at which memory is written to the host cache.

Answer 58

ESXTOP LLSWW/s

Question 59

Measured in megabytes, these counters represent the rate at which the ESXi host is swapping memory in from disk (SWR/s) and swapping memory out to disk (SWW/s).

Answer 59

ESXTOP SWR/s and SWW/s:

Question 60

The amount of swap space currently used by the VM.

Answer 60

ESXTOP SWCUR:

Question 61

The amount of swap space that the host expects the VM to use.

Answer 61

ESXTOP SWTGT: