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 <j...@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
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
