From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Giangiacomo Mariotti <gg.mariotti@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BTRFS: Unbelievably slow with kvm/qemu
Date: Sun, 11 Jul 2010 22:54:12 -0700 [thread overview]
Message-ID: <4C3AAE04.8060309@gmail.com> (raw)
In-Reply-To: <AANLkTin1uF6WbVvxJ84oO1NKnCU-6VHrmWU1XFYTlqtp@mail.gmail.com>
On 07/11/2010 10:24 PM, Giangiacomo Mariotti wrote:
> Hi, is it a known problem how much slow is Btrfs with kvm/qemu(meaning
> that the image kvm/qemu uses as the hd is on a partition formatted
> with Btrfs, not that the fs used by the hd inside the kvm environment
> is Btrfs, in fact inside kvm the / partition is formatted with ext3)?
> I haven't written down the exact numbers, because I forgot, but while
> I was trying to make it work, after I noticed how much longer than
> usual it was taking to just install the system, I took a look at iotop
> and it was reporting a write speed of the kvm process of approximately
> 3M/s, while the Btrfs kernel thread had an approximately write speed
> of 7K/s! Just formatting the partitions during the debian installation
> took minutes. When the actual installation of the distro started I had
> to stop it, because it was taking hours! The iotop results made me
> think that the problem could be Btrfs, but, to be sure that it wasn't
> instead a kvm/qemu problem, I cut/pasted the same virtual hd on an
> ext3 fs and started kvm with the same parameters as before. The
> installation of debian inside kvm this time went smoothly and fast,
> like normally it does. I've been using Btrfs for some time now and
> while it has never been a speed champion(and I guess it's not supposed
> to be one and I don't even really care that much about it), I've never
> had any noticeable performance problem before and it has always been
> quite stable. In this test case though, it seems to be doing very bad.
>
> cheers
>
not sure with butter filesystems.. but, what is the last good kernel?
are you able to bisect?
Justin P. Mattock
next prev parent reply other threads:[~2010-07-12 5:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 5:24 BTRFS: Unbelievably slow with kvm/qemu Giangiacomo Mariotti
2010-07-12 5:54 ` Justin P. Mattock [this message]
2010-07-12 7:09 ` Michael Tokarev
2010-07-12 7:17 ` Justin P. Mattock
2010-07-12 13:15 ` Giangiacomo Mariotti
2010-07-12 13:34 ` Giangiacomo Mariotti
2010-07-12 13:40 ` Michael Tokarev
2010-07-12 13:43 ` Josef Bacik
2010-07-12 13:42 ` Michael Tokarev
2010-07-12 13:49 ` Josef Bacik
2010-07-12 20:23 ` Giangiacomo Mariotti
2010-07-12 20:24 ` Josef Bacik
2010-07-13 8:53 ` [Qemu-devel] " Kevin Wolf
2010-07-13 4:29 ` Avi Kivity
2010-07-14 2:39 ` Giangiacomo Mariotti
2010-07-14 19:49 ` Christoph Hellwig
2010-07-17 5:29 ` Giangiacomo Mariotti
2010-07-17 10:28 ` Ted Ts'o
2010-07-18 7:15 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2010-08-29 19:34 Tomasz Chmielewski
2010-08-30 0:14 ` Josef Bacik
2010-08-30 15:59 ` K. Richard Pixley
2010-08-31 21:46 ` Mike Fedyk
2010-08-31 22:01 ` K. Richard Pixley
[not found] ` <4C7D7B14.9020008@noir.com>
2010-09-02 0:18 ` Ted Ts'o
2010-09-02 16:36 ` K. Richard Pixley
2010-09-02 16:49 ` K. Richard Pixley
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=4C3AAE04.8060309@gmail.com \
--to=justinmattock@gmail.com \
--cc=gg.mariotti@gmail.com \
--cc=linux-kernel@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