xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* Estimating CPU utilization of DomU
@ 2010-07-16  0:59 Gaurav Dhiman
  2010-07-16  8:19 ` Atsushi SAKAI
  0 siblings, 1 reply; 3+ messages in thread
From: Gaurav Dhiman @ 2010-07-16  0:59 UTC (permalink / raw)
  To: xen-devel

Hi All,

I am trying to implement a small script to estimate the CPU
utilization of my DomU's from Domain-0 using libvirt APIs. I am using
the virDomainInfo structure for that:

struct virDomainInfo{
unsigned char	state	: the running state, one of virDomainState
unsigned long	maxMem	: the maximum memory in KBytes allowed
unsigned long	memory	: the memory in KBytes used by the domain
unsigned short	nrVirtCpu	: the number of virtual CPUs for the domain
unsigned long long	cpuTime	: the CPU time used in nanoseconds
}

So basically I query this structure for my DomU's every 'n' seconds,
and get the CPU utilization by taking the difference of cpuTime (in
seconds) and diving it by 'n'. To verify my estimates, I am running
sar inside my DomU's (I do 100-%idle to estimate CPU util). It works
perfectly for CPU intensive DomU's, but I observe some discrepancies
for I/O intensive DomU's. My scripts shows higher CPU utilization than
the sar output. Sometimes the difference is close to 10-15%. I am not
sure what is the reason for this? Is there some time which the DomU
VCPUs spend running, which sar cannot see? Or does the libvirt API add
up the time spent by domain-0 for work done on behalf of DomU to its
structure?

Any insights here would be really helpful!

Thanks,
-Gaurav

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-07-16 23:28 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-07-16  0:59 Estimating CPU utilization of DomU Gaurav Dhiman
2010-07-16  8:19 ` Atsushi SAKAI
2010-07-16 23:28   ` Gaurav Dhiman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).