Hi everyone,
I am studying the Xen performance metrics.
My question is if we can get the following metrics from Xen hypervisor interface / XEND API (XEN management API) or not ?
cpu.extra.summation, cpu.ready.summation,
disk.busResets.summation, disk.commandsAborted.summation, disk.queueLatency.average,
mem.active.average, mem.overhead.average
If no, plan to add them? or How to add them?
As I study, there are the following results about XEN performance metrics on the current XEN 4.1.0.
BTW, VMWARE hypervisor can get all the metrics below.
We can determine if the VM / host encounter the bottleneck issues using the performance metrics.
| Xen (hypervisor) interface | Xen enabled kernel (drivers like balloon, network / block backend, privcmd,…) | XEN (management) API (XEND API) | Libvirt API |
CPU | | | | |
1. cpu.extra.summation | | | | |
2. cpu.ready.summation | | | | |
3. cpu.usagemhz.average | v | x | V | V |
disk | | | | |
4. disk.busResets.summation | | | | |
5.disk.commandsAborted.summation | | | | |
6. disk.totalLatency.average | | | | |
7. disk.queueLatency.average | | | | |
Throughput: An average of 8. disk.read.average and 9. disk.write.average 10. disk throughput = (disk.read.average + disk.write.average ) /2 | x | v | V | V |
memory | | | | |
11. mem.active.average | | | | |
12. mem.consumed.average | v | x | V | V |
13. mem.overhead.average | | | | |
Memory Swapping: 14. mem.swapin.average, 15. mem.swapout.average 16. mem.swapped.average | v | x | x | V |
17.mem.vmmemctl.average(balloon) | x | v | x | V |
network | | | | |
18. net.received.average, 19. net.transmitted.average and 20. net.usage.average | x | v | V | V |
Thanks.
YJ