From: Jim Salter <jim@jrs-s.net>
To: Rich Freeman <r-btrfs@thefreemanclan.net>
Cc: Gert Menke <gert@menke.ac>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS as image store for KVM?
Date: Fri, 25 Sep 2015 08:56:02 -0400 [thread overview]
Message-ID: <56054462.10103@jrs-s.net> (raw)
In-Reply-To: <CAGfcS_=bst0S8YLsr6y4oGDu7Gy-ox9ow5+_nD4c3zFdj-Y6ug@mail.gmail.com>
I suspect that the answer most likely boils down to "the ARC".
ZFS uses an Adaptive Replacement Cache instead of a standard FIFO, which
keeps blocks in cache longer if they have been accessed in cache. This
means much higher cache hit rates, which also means minimizing the
effects of fragmentation.
That's an off-the-top-of-my-head guess, though. All I can tell you for
certain is that I've done both - KVM stores on btrfs and on ZFS (and on
LVM and on mdraid and...) - and it works extremely, extremely well on
ZFS for long periods of time, where with btrfs it works very well at
first but then degrades rapidly.
FWIW I've been using KVM + ZFS in wide production (>50 hosts) for 5+
years now.
On 09/25/2015 08:48 AM, Rich Freeman wrote:
> On Sat, Sep 19, 2015 at 9:26 PM, Jim Salter <jim@jrs-s.net> wrote:
>> ZFS, by contrast, works like absolute gangbusters for KVM image storage.
> I'd be interested in what allows ZFS to handle KVM image storage well,
> and whether this could be implemented in btrfs. I'd think that the
> fragmentation issues would potentially apply to any COW filesystem,
> and if ZFS has a solution for this then it would probably benefit
> btrfs to implement the same solution, and not just for VM images.
>
> --
> Rich
next prev parent reply other threads:[~2015-09-25 12:56 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 21:34 BTRFS as image store for KVM? Gert Menke
2015-09-16 3:00 ` Chris Murphy
2015-09-16 3:57 ` Duncan
2015-09-16 11:35 ` Brendan Heading
2015-09-16 12:25 ` Austin S Hemmelgarn
2015-09-16 12:41 ` Paul Jones
2015-09-17 17:56 ` Gert Menke
2015-09-17 18:35 ` Chris Murphy
2015-09-17 21:32 ` Gert Menke
2015-09-18 2:00 ` Duncan
2015-09-18 8:32 ` Gert Menke
2015-09-23 7:28 ` Russell Coker
2015-09-18 14:13 ` Austin S Hemmelgarn
2015-09-23 7:24 ` Russell Coker
2015-09-17 18:46 ` Mike Fleetwood
2015-09-17 19:43 ` Hugo Mills
2015-09-17 21:49 ` Gert Menke
2015-09-18 2:22 ` Duncan
2015-09-18 8:59 ` Gert Menke
2015-09-17 22:41 ` Sean Greenslade
2015-09-18 7:34 ` Gert Menke
2015-09-17 4:19 ` Paul Harvey
2015-09-20 1:26 ` Jim Salter
2015-09-25 12:48 ` Rich Freeman
2015-09-25 12:56 ` Jim Salter [this message]
2015-09-25 13:04 ` Austin S Hemmelgarn
[not found] ` <5605483A.7040103@jrs-s.net>
2015-09-25 13:46 ` Austin S Hemmelgarn
2015-09-25 13:52 ` Jim Salter
2015-09-25 14:02 ` Timofey Titovets
2015-09-25 14:20 ` Austin S Hemmelgarn
2015-09-29 14:12 ` Gert Menke
2015-10-02 4:21 ` Russell Coker
2015-10-02 12:07 ` Austin S Hemmelgarn
2015-10-03 8:32 ` Russell Coker
2015-10-04 2:09 ` Duncan
2015-10-04 12:03 ` Lionel Bouton
2015-10-04 12:21 ` Rich Freeman
2015-10-05 8:19 ` Duncan
2015-10-05 8:43 ` Erkki Seppala
2015-10-05 8:51 ` Roman Mamedov
2015-10-05 11:16 ` Lionel Bouton
2015-10-05 11:40 ` Rich Freeman
2015-10-05 11:54 ` Austin S Hemmelgarn
[not found] ` <RPG31r00t34oj7R01PG5Us>
2015-10-05 14:04 ` Duncan
2015-10-05 15:59 ` Austin S Hemmelgarn
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=56054462.10103@jrs-s.net \
--to=jim@jrs-s.net \
--cc=gert@menke.ac \
--cc=linux-btrfs@vger.kernel.org \
--cc=r-btrfs@thefreemanclan.net \
/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.