From: Mike Fleetwood <mike.fleetwood@googlemail.com>
To: MegaBrutal <megabrutal@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS and databases
Date: Wed, 1 Aug 2018 09:59:28 +0100 [thread overview]
Message-ID: <CAMU1PDhnM1vL9OZ-ytw-00vwQXPSTHpCpiB25o3FfoAL-iy0bw@mail.gmail.com> (raw)
In-Reply-To: <CAE8gLhm96B1xxoMv=sYuaNeLYRDP3YUw2qsKumpjLm+jJVjfQQ@mail.gmail.com>
On 1 August 2018 at 04:45, MegaBrutal <megabrutal@gmail.com> wrote:
> But there is still one question that I can't get over: if you store a
> database (e.g. MySQL), would you prefer having a BTRFS volume mounted
> with nodatacow, or would you just simply use ext4?
>
> I know that with nodatacow, I take away most of the benefits of BTRFS
> (those are actually hurting database performance – the exact CoW
> nature that is elsewhere a blessing, with databases it's a drawback).
> But are there any advantages of still sticking to BTRFS for a database
> albeit CoW is disabled, or should I just return to the old and
> reliable ext4 for those applications?
Also note that no data CoW implies no data checksums too.
https://btrfs.wiki.kernel.org/index.php/FAQ#Can_I_have_nodatacow_.28or_chattr_.2BC.29_but_still_have_checksumming.3F
Mike
next prev parent reply other threads:[~2018-08-01 10:44 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
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 [this message]
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=CAMU1PDhnM1vL9OZ-ytw-00vwQXPSTHpCpiB25o3FfoAL-iy0bw@mail.gmail.com \
--to=mike.fleetwood@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--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).