From: Matthew Tippett <tippettm@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Avi Kivity <avi@redhat.com>, RW <kvm@tauceti.net>, kvm@vger.kernel.org
Subject: Re: sync guest calls made async on host - SQLite performance
Date: Tue, 29 Sep 2009 15:32:11 -0400 [thread overview]
Message-ID: <4AC260BB.3090906@gmail.com> (raw)
In-Reply-To: <4AC259DC.2080807@codemonkey.ws>
Okay, bringing the leafs of the discussions onto this thread.
As per
http://www.phoronix.com/scan.php?page=article&item=linux_2631_kvm&num=1&single=1
"The host OS (as well as the guest OS when testing under KVM) was
running an Ubuntu 9.10 daily snapshot with the Linux 2.6.31 (final) kernel"
I am attempting to get the actual "daily" snapshot to provide the
precise version. I should have that information shortly. It is likely
that it was within 1-2 weeks prior to the article posting.
> Ubuntu's Karmic release has _not_ been released yet. For this
> particular test, Phoronix was probably using an alpha drop before
> Ubuntu switched from kvm-84 to qemu-kvm-0.11.0.
The "probably" was described above - it was a snapshot after the 2.6.31
final as September 9th, the article was published on September 21st, so
there is a finite window.
I have high confidence in the testing that Phoronix has done and don't
expect to need to confirm the results explicitly, and I have pieced
together the following information. I should be able to get the actual
daily build number but broadly it looks like it was
Ubuntu 9.10 daily snapshot (~ 9th - 21st September)
Linux 2.6.31 (packaged as 2.6.31-10.30 to 2.6.31-10.32)
qemu-kvm 0.11 (packaged as 0.11.0~rc2-0ubuntu to 0.11.0~rc2-0ubuntu5
Once I get confirmation of the actual date, digger deeping can occur.
But, if it turned out to be Ubuntu 9.10, linux 2.6.31, qemu-kvm 0.11
would there be any concerns?
I would prefer rather than riling against Phoronix or the results as
presented, ask questions to seek further information about what was
tested rather than writing off all of it as completely invalid.
Regards,
Matthew
-------- Original Message --------
Subject: Re: sync guest calls made async on host - SQLite performance
From: Anthony Liguori <anthony@codemonkey.ws>
To: Matthew Tippett <tippettm@gmail.com>
Cc: Avi Kivity <avi@redhat.com>, RW <kvm@tauceti.net>, kvm@vger.kernel.org
Date: 09/29/2009 03:02 PM
> Matthew Tippett wrote:
>> I have created a launchpad bug against qemu-kvm in Ubuntu.
>>
>> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/437473
>>
>> Just re-iterating, my concern isn't so much performance, but integrity
>> of stock KVM configurations with server or other workloads that expect
>> sync fileIO requests to be honored and synchronous to the underlying
>> physical disk.
>>
>> (That and ensuring that sanity reigns where a benchmark doesn't show a
>> guest operating 10 times faster than a host for the same test :).
>
> And I've closed it. In the future, please actually reproduce a bug
> before filing it. Reading it on a website doesn't mean it's true :-)
>
> Regards,
>
> Anthony Liguori
next prev parent reply other threads:[~2009-09-29 19:32 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 7:00 sync guest calls made async on host - SQLite performance RW
2009-09-27 11:37 ` Avi Kivity
2009-09-27 12:07 ` Matthew Tippett
2009-09-29 19:02 ` Anthony Liguori
2009-09-29 19:32 ` Matthew Tippett [this message]
2009-09-29 20:46 ` Dustin Kirkland
2009-09-29 20:51 ` Anthony Liguori
2009-10-07 14:15 ` Matthew Tippett
2009-10-07 16:53 ` Matthew Tippett
2009-10-07 18:59 ` Dustin Kirkland
2009-10-07 19:31 ` Matthew Tippett
2009-10-07 20:12 ` Avi Kivity
2009-10-07 21:01 ` Matthew Tippett
2009-10-09 6:05 ` Dustin Kirkland
[not found] ` <4ACE0196.9010904@gmail.com>
[not found] ` <d9c105ea0910082312n7218e1abhc69a2be660838e89@mail.gmail.com>
[not found] ` <f28b49ce0910090425p385636c3he6dfb7595927d7e4@mail.gmail.com>
2009-10-09 15:18 ` Dustin Kirkland
2009-10-09 19:06 ` Matthew Tippett
2009-10-11 9:16 ` Avi Kivity
2009-10-13 22:37 ` Christoph Hellwig
2009-10-14 11:03 ` Avi Kivity
2009-10-14 12:03 ` [PATCH] virtio-blk: fallback to draining the queue if barrier ops are not supported Avi Kivity
2009-10-14 14:46 ` Javier Guerra
2009-10-14 16:53 ` Avi Kivity
2009-10-14 15:38 ` Michael Tokarev
2009-10-14 15:46 ` Christoph Hellwig
2009-10-14 13:41 ` sync guest calls made async on host - SQLite performance Christoph Hellwig
2009-10-14 16:56 ` Avi Kivity
2009-10-14 17:02 ` Christoph Hellwig
2009-10-14 22:54 ` Anthony Liguori
2009-10-14 23:37 ` Avi Kivity
2009-10-15 12:17 ` Christoph Hellwig
2009-10-15 12:36 ` Christoph Hellwig
2009-10-19 5:56 ` Avi Kivity
2009-10-13 23:08 ` Anthony Liguori
2009-10-14 2:09 ` Matthew Tippett
2009-10-14 4:12 ` Dustin Kirkland
2009-10-14 11:32 ` Matthew Tippett
-- strict thread matches above, loose matches on Subject: below --
2009-09-25 2:11 Ian Woodstock
2009-09-25 3:13 ` Matthew Tippett
2009-09-23 15:58 Matthew Tippett
2009-09-24 11:44 ` Avi Kivity
2009-09-24 12:31 ` Matthew Tippett
2009-09-24 13:03 ` Avi Kivity
2009-09-24 19:49 ` Matthew Tippett
2009-09-25 7:22 ` Avi Kivity
2009-09-25 11:33 ` Matthew Tippett
2009-09-25 15:04 ` Avi Kivity
2009-09-29 18:58 ` Anthony Liguori
2009-09-29 18:57 ` Anthony Liguori
2009-09-29 18:54 ` Anthony Liguori
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=4AC260BB.3090906@gmail.com \
--to=tippettm@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@tauceti.net \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).