All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] slow speed for virtio-scsi since qemu 2.2
Date: Mon, 16 Feb 2015 15:44:31 +0100	[thread overview]
Message-ID: <54E2024F.9040501@redhat.com> (raw)
In-Reply-To: <54E20226.8090103@profihost.ag>



On 16/02/2015 15:43, Stefan Priebe - Profihost AG wrote:
> Hi,
> 
> Am 16.02.2015 um 13:24 schrieb Paolo Bonzini:
>>
>>
>> On 15/02/2015 19:46, Stefan Priebe wrote:
>>>
>>> while i get a constant random 4k i/o write speed of 20.000 iops with
>>> qemu 2.1.0 or 2.1.3. I get jumping speeds with qemu 2.2 (jumping between
>>> 500 iops and 15.000 iop/s).
>>>
>>> If i use virtio instead of virtio-scsi speed is the same between 2.2 and
>>> 2.1.
>>
>> http://wiki.qemu.org/Contribute/ReportABug
>>
>> What is your command line?
> 
> Could it be that this is a results of compiling qemu with --enable-debug
> to get debugging symbols?

Yes.

Paolo

  reply	other threads:[~2015-02-16 14:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 18:46 [Qemu-devel] slow speed for virtio-scsi since qemu 2.2 Stefan Priebe
2015-02-16 11:06 ` Alexandre DERUMIER
2015-02-16 12:24 ` Paolo Bonzini
2015-02-16 14:43   ` Stefan Priebe - Profihost AG
2015-02-16 14:44     ` Paolo Bonzini [this message]
2015-02-16 14:47       ` Stefan Priebe - Profihost AG
2015-02-16 14:49         ` Paolo Bonzini
2015-02-16 15:41           ` Stefan Priebe - Profihost AG
2015-02-16 15:49             ` Paolo Bonzini
2015-02-16 19:02               ` Stefan Priebe
2015-02-16 15:50             ` Andreas Färber
2015-02-16 19:02               ` Stefan Priebe
2015-02-16 14:58         ` Andrey Korolyov
2015-02-16 15:38           ` Stefan Priebe - Profihost AG

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=54E2024F.9040501@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=s.priebe@profihost.ag \
    /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.