[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] tap:aio / blktap slowness

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Ray Barnes" <rrb@xxxxxxxxxxxx>
  • Date: Fri, 9 Nov 2007 10:45:36 -0500
  • Delivery-date: Mon, 19 Nov 2007 09:55:53 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=FTQVhTwhDxWTAv4wMKwE2eCY7Wu9kPbSKPHnnXDNkhBTh76TCLeSA824AlrbivxURTa64Z+ytGioNtuVPcjyEHQt4HP/nwdVNsNaiiHMhvj9H/EItyTrnlCnSLT6wnVNTRxYay6vrrkeAjGIALut2GKAQ6z5cXCO61zr/4pr7ag=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Can anyone explain to me why tap:aio sucks so badly?
We've got numerous CentOS 5 dom0s running file-backed domUs with tap:aio.  The moment any one of them starts doing something disk-intensive, idle CPU in dom0 decreases, iowait increases, and disk IO for every other domU on the system suffers.  Where lies the problem, and what to do about it?
Ray Barnes
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.