Xen project Mailing List

Re: [Xen-users] decreasing Xenmon overhead

To: "Ashish Gupta" <ashishgup@xxxxxxxxx>

From: "Diwaker Gupta" <diwaker.lists@xxxxxxxxx>

Date: Tue, 29 May 2007 15:49:42 -0700

Delivery-date: Tue, 29 May 2007 15:48:01 -0700

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jNypbNfA0fv4nFJ1gmwSEH7uQDJZ6VYZKFMO38w/ZZHEZfZbB2sSBncSGVsQ5CZeyOY2Tn01nNofuJVfx8Ve+mSkSfIcRcf8+5kpIoYG6yq7rxmN3S+UlV54pl7K3w+HcgfEE8fqJBDohmAtgqvliE/IpXpXt9ClI6lRR2YfFN8=

List-id: Xen user discussion <xen-users.lists.xensource.com>

Ashish,

for offline analysis. However  I notice that at an interval of 100 ms or so
the overhead imposed by dom0 is quite high , with upto 40% of CPU
utilization.

Are you sure that the overhead is due to xenmon? What CPU utilization do you see in Domain 0 for the same workload, but without xenmon?

 Are there ways I can drastically reduce this overhead ? I read somwhere
about event overhead, using event masks and python overhead,  but am not
really sure how to use this information to reduce the overhead.

Exactly what metrics are you interested in monitoring? You might want to look at 'xentrace --help' and 'xentrace -e'. Basically you want the minimal set of events that will give you the desired information. To see available events, look at /usr/include/xen/trace.h HTH, Diwaker -- Web/Blog/Gallery: http://floatingsun.net/blog _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.