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

[Xen-users] xen 3.3 -> tap:aio performance over nfs


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: C V <rayvittal-lists@xxxxxxxxx>
  • Date: Fri, 30 Jan 2009 18:04:47 -0800 (PST)
  • Delivery-date: Fri, 30 Jan 2009 18:05:30 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=o/SL3LMcbNzoSUudYbhBiv8flyZ0+dPioAUX/WKu564ZVw2VOkhWT9oVXL8h419RNMEmZ29mKV5wJ6KdNHMrqg1hd1LOB1dGAn7zRoevbgA4gv/6j1KoeN8q4cv2dkLVFFTC1Gb1XnIYuM8K4jb1rJCQd9aW8nJpewpgjjlU5I4=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I've been getting disappointing performance for file-backed disks mounted using 
tap:aio over an NFS mount. 
For example, bonnie++ reports 3 MB/s for block writes in the domU to
that
disk, but in dom0, bonnie++ reports 38 MB/s for that same mount. The
same domU can get 40 MB/s to the same filer using a phy: block device
over iSCSI .

It seems that 
1. tap:aio causes synchronous writes to the nfs mount (6 writes, wait for ack, 
write 6 more etc) as opposed to NFSv3 async write
2. Each synchronous write writes very small blocks (4K bytes vs max of 32K 
bytes)

Is there any configuration option to tweak this behavior to get 
better-performing async writes to the filer?

Thanks
--
CV

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


 


Rackspace

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