Measuring Co-Stop (vSMP) Usage in Proxmox

[Tmanok]

Hey Everyone,

Back from ESXi-land with another valuable question, well two in fact. The question in the title is about measuring CPU resource usage in more detail, for example in Proxmox I love that there is an oi-delay counter.
Questions:

1. How would one go about measuring something like Co-Stop in Proxmox? (QEMU)
2. Is the io-delay in Proxmox simply the latency of storage access, or is it the the latency of data going directly to the CPU for processing (aka iowait)
   https://support.hpe.com/hpesc/public/docDisplay?cc=us&docId=c02783994&lang=en-us I personally use "sar" and "glances" to show my VM's iowait internally, but I would love to see this in the console if it is not the same as io-delay seen on the hypervisor host. #FeatureRequest

Thanks everyone!
Tmanok

 

[Alwin]

How would one go about measuring something like Co-Stop in Proxmox? (QEMU)

I think co-stop is VMware specific. The linux kernel takes care of the scheduling of the KVM process. A monitoring tool, like netdata or others could give you long term measures.

Is the io-delay in Proxmox simply the latency of storage access, or is it the the latency of data going directly to the CPU for processing (aka iowait)
https://support.hpe.com/hpesc/public/docDisplay?cc=us&docId=c02783994&lang=en-us I personally use "sar" and "glances" to show my VM's iowait internally, but I would love to see this in the console if it is not the same as io-delay seen on the hypervisor host. #FeatureRequest

It's the IO wait.