From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=54844 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PngUW-0008N0-8L
	for qemu-devel@nongnu.org; Thu, 10 Feb 2011 19:04:20 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1PngUU-0005rk-55
	for qemu-devel@nongnu.org; Thu, 10 Feb 2011 19:04:03 -0500
Received: from mx1.redhat.com ([209.132.183.28]:37279)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mtosatti@redhat.com>) id 1PngUT-0005qu-Sz
	for qemu-devel@nongnu.org; Thu, 10 Feb 2011 19:04:02 -0500
Date: Thu, 10 Feb 2011 22:03:02 -0200
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 2/7] Enable I/O thread and VNC threads
	by default
Message-ID: <20110211000302.GA15682@amt.cnet>
References: <4D5113D3.9090802@aurel32.net> <4D511500.1040303@siemens.com>
	<4D5115C2.6060008@aurel32.net> <4D51842C.8000209@codemonkey.ws>
	<4D5125E2.8090902@aurel32.net> <4D5132C3.1040900@redhat.com>
	<4D5145A4.1070904@aurel32.net> <4D515C6C.9000407@aurel32.net>
	<20110209173523.GJ16429@hall.aurel32.net>
	<4D52F418.7070000@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <4D52F418.7070000@codemonkey.ws>
Content-Transfer-Encoding: quoted-printable
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>, Jan Kiszka <jan.kiszka@siemens.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Anthony Liguori <aliguori@linux.vnet.ibm.com>, Paul Brook <paul@codesourcery.com>, "Edgar E. Iglesias" <edgar.iglesias@gmail.com>, Paolo Bonzini <pbonzini@redhat.com>, Aurelien Jarno <aurelien@aurel32.net>, Arun Bharadwaj <arun@linux.vnet.ibm.com>

On Wed, Feb 09, 2011 at 09:07:52PM +0100, Anthony Liguori wrote:
> On 02/09/2011 06:35 PM, Aurelien Jarno wrote:
> >On Tue, Feb 08, 2011 at 04:08:28PM +0100, Aurelien Jarno wrote:
> >>Aurelien Jarno a =E9crit :
> >>>Paolo Bonzini a =E9crit :
> >>>>On 02/08/2011 12:15 PM, Aurelien Jarno wrote:
> >>>>>however
> >>>>>it should not be done ignoring all the*current*  drawbacks of the
> >>>>>iothread mode. We know them (at least for some of them), so let's =
try to
> >>>>>solve them.
> >>>>Let's also enumerate them.
> >>>>
> >>> From what I know:
> >>>- performance regression in TCG mode
> >>I setup an x86_64 guest on an x86_64 host (Intel Xeon E5345). Nothing
> >>was running except the standard daemons and the CPU governor was set =
to
> >>"performance" on all CPU. I then compared the network performance usi=
ng
> >>netperf in default mode, through a tap interface and a virtio nic. I =
got
> >>the following results (quite reproducible, std below 0.5):
> >>- without IO thread: 107.36 MB/s
> >>- with IO thread:     89.93 MB/s
> >>
> >And the same test on the code from september 2009:
> >- without IO thread: 141.8 MB/s
> virtio-net is super finicky regarding mitigation strategies and
> their relationship to the I/O thread.  Different benchmarks will
> behave differently.  virtio-blk is probably a better device to test
> as you'll get much more consistent results across different type of
> I/O patterns.

netperf server on guest, RHEL5.4 guest (e1000), uq/master branch, TCG:

iothread: 236MB/s
no iothread: 215MB/s

Also noticed scp was slightly faster with iothread earlier this week,
don't remember numbers.