WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Detecting I/O contention

To: Xen User List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Detecting I/O contention
From: "John A. Sullivan III" <jsullivan@xxxxxxxxxxxxxxxxxxx>
Date: Sat, 11 Nov 2006 12:55:30 -0500
Delivery-date: Sat, 11 Nov 2006 09:56:34 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
We are experiencing cripplingly slow performance in some of our domUs on
a Xen 2.0.7 host.  There is plenty of CPU available, plenty of RAM and
plenty of disk space.  We suspect the issue is either network or disk
I/O contention.  How does one detect excessive disk or network I/O
contention in Xen?

We do notice the "event" process in the dom0 frequently consuming 40% to
50% of the CPU cycles.  I assume this is a bad thing. Is that correct?
-- 
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan@xxxxxxxxxxxxxxxxxxx

If you would like to participate in the development of an open source
enterprise class network security management system, please visit
http://iscs.sourceforge.net


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Detecting I/O contention, John A. Sullivan III <=