From: Anthony Liguori <anthony@codemonkey.ws>
To: Matthew Tippett <tippettm@gmail.com>
Cc: Dustin Kirkland <dustin.kirkland@gmail.com>,
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, 13 Oct 2009 18:08:51 -0500 [thread overview]
Message-ID: <4AD50883.1040305@codemonkey.ws> (raw)
In-Reply-To: <4ACF89CB.5020406@gmail.com>
Matthew Tippett wrote:
> Thanks Duncan for reproducing the behavior outside myself and Phoronix.
>
> I dug deeper into the actual syscalls being made by sqlite. The
> salient part of the behaviour is small sequential writes followed by a
> fdatasync (effectively a metadata-free fsync).
>
> As Dustin indicates,
>
> if scsi is used, you incur the cost of virtualization,
> if virtio is used, your guests fsyncs incur less cost.
>
> So back to the question to the kvm team. It appears that with the
> stock KVM setup customers who need higher data integrity (through
> fsync) should steer away from virtio for the moment.
>
> Is that assessment correct?
No, it's an absurd assessment.
You have additional layers of caching happening because you're running a
guest from a filesystem on the host.
A benchmark running under a guest that happens do be faster than the
host does not indicate anything. It could be that the benchmark is
poorly written.
What operation, specifically, do you think is not behaving properly
under kvm? ext4 (karmic's default filesystem) does not enable barriers
by default so it's unlikely this is anything barrier related.
> Regards,
>
> Matthew
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-10-13 23:09 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
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 [this message]
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=4AD50883.1040305@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=dustin.kirkland@gmail.com \
--cc=kvm@tauceti.net \
--cc=kvm@vger.kernel.org \
--cc=tippettm@gmail.com \
/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).