From: ein <ein.net@gmail.com>
To: Martin Steigerwald <martin@lichtvoll.de>,
Hugo Mills <hugo@carfax.org.uk>
Cc: MegaBrutal <megabrutal@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS and databases
Date: Thu, 2 Aug 2018 12:15:16 +0200 [thread overview]
Message-ID: <097d723a-5bc3-1256-d7ac-a493c55e974b@gmail.com> (raw)
In-Reply-To: <2861903.YXSMuvecdq@merkaba>
On 08/02/2018 11:16 AM, Martin Steigerwald wrote:
> However I wonder: Is this it? Is there nothing that can be improved in
> BTRFS to handle database and VM files in a better way, without altering
> any default settings?
Poor performance is not the biggest BTRFS problem, it's known for silent data corruption for
instance when using KVM with cache=none,aio=native, error counters are worthless too and do not
increment in case of csum mismatches. Performance penalty is huge, iowait for 4x SSD on RAID10 with
BTRFS is the same like when using RAID1 on 2xSAS with Ext4 for firebird database ~ 20GB which can
fit as a whole in RAM for better read performance.
next prev parent reply other threads:[~2018-08-02 12:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 3:45 BTRFS and databases MegaBrutal
2018-08-01 8:48 ` Duncan
2018-08-01 8:56 ` Hugo Mills
2018-08-02 9:16 ` Martin Steigerwald
2018-08-02 10:15 ` ein [this message]
2018-08-02 10:35 ` Andrei Borzenkov
2018-08-02 10:42 ` Martin Steigerwald
2018-08-02 10:53 ` Qu Wenruo
2018-08-01 8:59 ` Mike Fleetwood
2018-08-01 11:21 ` Adam Borowski
2018-08-01 12:19 ` Austin S. Hemmelgarn
2018-08-01 14:33 ` Remi Gauvin
2018-08-02 7:07 ` Qu Wenruo
2018-08-02 12:32 ` Remi Gauvin
2018-08-02 7:02 ` Qu Wenruo
2018-08-02 10:45 ` Andrei Borzenkov
2018-08-02 10:56 ` Qu Wenruo
2018-08-02 12:27 ` Austin S. Hemmelgarn
2018-08-02 13:14 ` Martin Raiber
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=097d723a-5bc3-1256-d7ac-a493c55e974b@gmail.com \
--to=ein.net@gmail.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=megabrutal@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).