What is ESXTOP ?
its a very fantastic and helpful tool , it used for troubleshoot performance issues it can help you to explain the performance in CPU , Memory , Network and storage
we will talk about every thing of this in individual article But now we will explain all thing in a small preview
At first How to access ESXTOP
JUST you want to open SSH on you Host and log in it by putty
write ROOT and PASSWORD for Authentication
Now you are ready to write Your Command esxtop
What you are looking at is the CPU screen in ESXTOP and you are now looking for CPU specific counters. You can browse around through different pages.
When troubleshooting CPU performance for your virtual machines the following counters are the most important.
%USED, %RDY, %CSTP
%USED tells you how much time did the virtual machine spend executing CPU cycles on the physical CPU.
%RDY is a Key Performance Indicator! Always start with this one. This one defines how much time your virtual machine wanted to execute CPU cycles but could not get access to the physical CPU. It tells you how much time did you spend in a “queue”. I normally expect this value to be better than 5% (this equals 1000ms in the vCenter Performance Graphs .
%CSTP tells you how much time a virtual machine is waiting for a virtual machine with multiple vCPU to catch up. If this number is higher than 3% you should consider lowering the amount of vCPU in your virtual machine.
TO Go to memory Page Just press M .
When troubleshooting memory performance this is the counters you want to focus on from a virtual machine perspective .
MCTL, MCTLSZ, SWCUR, SWR/s, SWW/s
MCTL? This column is either YES or NO.If Yes it means that the balloon driver is installed. The Balloon driver is automatically installed with VMware tools and should be in every virtual machine. If it says No in this column then figure out why.
MCTLSZ The column show you how inflated the balloon is in the virtual machine. If it says 500MB it translates to the balloon driver inside the guest operating system has “stolen” 500MB from Windows/Linux etc. You would expect to see a value of 0 (zero) in this column
SWCUR tells you how much memory the virtual machine has in the .vswp file. If you see a number of 500MB here it means that 500MB is from the swap file. This does not necessarily equals to bad performance. To figure out if you virtual machine is suffering from hypervisor swapping you need to look at the next two counters. In a healthy environment you would want this value to på 0 (zero)
SWR/s This value tells you the Read activity to your swap file. If you see a number here, then your virtual machine is suffering from hypervisor swapping.
SWW/s This value tells you the Write activity to your swap file. You want to see the number 0 (zero) here. Every number above 0 is BAD.
For Network Page Just press N
you show from here every thing about network and with which port that VM machine connected and with which NIC was connected .
in the near Future we will talk about Memory CPU and Network one by one in individual article