All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Wangting (Kathy)" <kathy.wangting@huawei.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [question] the patch which affect performance of virtio-scsi
Date: Sun, 08 Feb 2015 11:10:24 +0100	[thread overview]
Message-ID: <54D73610.7080005@redhat.com> (raw)
In-Reply-To: <54D5F660.7030801@huawei.com>



On 07/02/2015 12:26, Wangting (Kathy) wrote:
> OK, Thank you very much for your detailed explanation.
> 
> But I have another question about the big change from qemu-1.5.3 to qemu-1.6.0-rc0.
> 
> When I use ramdisk for IO performance testing, the result is as follows.
> 
> [fio-test]          rw         bs         iodepth    jobs       bw         iops
> ------------------------------------------------------------------------------------
> qemu-1.5.3          read       4k         32          1         285MB/s    73208
> qemu-1.6.0-rc0      read       4k         32          1         253MB/s    64967
> 
> And virtio-blk is the same.
> 
> I know there are so many differences between qemu-1.5 and qemu-1.6, but I am confused about
> what new features impact the performance so much. Do you know it?

No, sorry.  Please try newer versions first and see if this was fixed.
QEMU 1.6 is more than a year old.

Paolo

  reply	other threads:[~2015-02-08 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03  2:31 [Qemu-devel] [question] the patch which affect performance of virtio-scsi Wangting (Kathy)
2015-02-03  2:56 ` Wangting (Kathy)
2015-02-03  8:49   ` Paolo Bonzini
2015-02-07 11:26     ` Wangting (Kathy)
2015-02-08 10:10       ` Paolo Bonzini [this message]
2015-02-09  2:53         ` Wangting (Kathy)
2015-02-03  8:42 ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54D73610.7080005@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kathy.wangting@huawei.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.