• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Why is %WAIT so high in esxtop?

Duncan Epping · Jul 17, 2012 ·

I got this question today around %WAIT and why it was so high for all these VMs. I grabbed a screenshot from our test environment. It shows %WAIT next to %VMWAIT.

First of all, I suggest looking at %VMWAIT. This one is more relevant in my opinion than %WAIT. %VMWAIT is a derivative of %WAIT, however it does not include %IDLE time but does include %SWPWT and the time the VM is blocked for when a device is unavailable. That kind of reveals immediately why  %WAIT seems extremely high, it includes %IDLE! Another thing to note is the %WAIT for a VM is multiple worlds collided in to a single metric. Let me show you what I mean:

As you can see 5 worlds, which explains the %WAIT time to be around 500% constantly when the VM is not doing much. Hope that helps…

<edit> I just got pointed to this great KB article by one of my colleagues. It explains various CPU metrics in-depth. Key take away from that article for me is the following: %WAIT + %RDY + %CSTP + %RUN = 100%. Note that this is per world! Thanks Daniel for pointing this out!</edit>

Related

Management & Automation, Server, Storage 5.0, esxtop, performance, troubleshooting, VMware, vSphere

Reader Interactions

Comments

  1. d_ says

    17 July, 2012 at 12:57

    Nice article on a new metric shown with esxtop 5.

    One metric i’m stuck on is %LAT_C, and how that differs to %RDY. The descriptions are very similar, yet i see quite a difference in the values displayed.

    Are you able to explain it?

    Cheers.
    d_

  2. Fly Moon says

    17 July, 2012 at 15:53

    Somebody asked the same question at:
    http://communities.vmware.com/message/2077455#2077455

  3. Duncan Epping says

    19 July, 2012 at 08:15

    @D_: Lat_C is a cumulative of various metrics. I will try to dig up which ones exactly.

  4. Fred Peterson says

    19 July, 2012 at 16:02

    Whats the point of %WAIT then if VMware finaly wised up and is giving us a wait value that is way more meaningful?

    I hate having to explain %WAIT when it includes a metric that is the opposite of what we actually care about.

    Even Microsoft was smart enough to exclude “System Idle Process” when telling us what the CPU usage is!

  5. Fred Peterson says

    19 July, 2012 at 16:03

    Yes I’m aware that %WAIT includes metrics that aren’t just about processor usage but thats not the point.

  6. Duncan Epping says

    19 July, 2012 at 16:43

    Not sure what your point is either Fred. ESXTOP is not a monitoring tool. It is there for troubleshooting, and metrics are simply not removed to provide backwards compatibility to 3rd party scripts / solutions using them.

  7. Fred Peterson says

    19 July, 2012 at 16:48

    I didn’t mean to imply %wait should be removed, rather is there any reason to even bother looking at the metric anymore to prove/disprove performance issues.

    • Duncan Epping says

      24 July, 2012 at 09:04

      Good question, I normally don’t bother any longer… as other metrics are a far better indication.

  8. Pawel says

    9 October, 2012 at 18:23

    Hm, I don’t understand one thing: when I expand a world I have 4 parts:

    vmware-vmx Wait 97 Idle 0
    vmn0:my_machine Wait 69 Idle 68
    vmware-vmx Wait 97 Idle 0
    mks:my_machhine Wait 97 Idle 0

    1. the ‘real’ wait time for my VM is 1% ?
    2. why the wait time for other things (vmx and mks) is so big? There is no idle to substract and is it around 97%

    Could you Duncan help me with that please?

    • OHenrard says

      11 February, 2014 at 12:29

      Hello, i’m wondering too in my systems

  9. damkus says

    2 June, 2014 at 15:01

    What is threshold for %VMWAIT ?

Primary Sidebar

About the author

Duncan Epping is a Chief Technologist in the Office of CTO of the Cloud Platform BU at VMware. He is a VCDX (# 007), the author of the "vSAN Deep Dive", the “vSphere Clustering Technical Deep Dive” series, and the host of the "Unexplored Territory" podcast.

Upcoming Events

May 24th – VMUG Poland
Aug 21st – VMware Explore
Sep 20th – VMUG DK
Nov 6th – VMware Explore
Dec 7th – Swiss German VMUG

Recommended Reads

Sponsors

Want to support Yellow-Bricks? Buy an advert!

Advertisements

Copyright Yellow-Bricks.com © 2023 · Log in