From: Tomasz Chmielewski <tch@virtall.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: very poor performance / a lot of writes to disk with space_cache (but not with space_cache=v2)
Date: Wed, 19 Sep 2018 10:43:18 +0200 [thread overview]
Message-ID: <e0f21dace16885d1bd615dd723235d57@virtall.com> (raw)
I have a mysql slave which writes to a RAID-1 btrfs filesystem (with
4.17.14 kernel) on 3 x ~1.9 TB SSD disks; filesystem is around 40% full.
The slave receives around 0.5-1 MB/s of data from the master over the
network, which is then saved to MySQL's relay log and executed. In ideal
conditions (i.e. no filesystem overhead) we should expect some 1-3 MB/s
of data written to disk.
MySQL directory and files in it are chattr +C (since the directory was
created, so all files are really +C); there are no snapshots.
Now, an interesting thing.
When the filesystem is mounted with these options in fstab:
defaults,noatime,discard
We can see a *constant* write of 25-100 MB/s to each disk. The system is
generally unresponsive and it sometimes takes long seconds for a simple
command executed in bash to return.
However, as soon as we remount the filesystem with space_cache=v2 -
writes drop to just around 3-10 MB/s to each disk. If we remount to
space_cache - lots of writes, system unresponsive. Again remount to
space_cache=v2 - low writes, system responsive.
That's a huuge, 10x overhead! Is it expected? Especially that
space_cache=v1 is still the default mount option?
Tomasz Chmielewski
https://lxadm.com
next reply other threads:[~2018-09-19 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 8:43 Tomasz Chmielewski [this message]
2018-09-19 9:33 ` very poor performance / a lot of writes to disk with space_cache (but not with space_cache=v2) Qu Wenruo
2018-09-19 12:00 ` Remi Gauvin
2018-09-19 17:58 ` Hans van Kranenburg
2018-09-19 20:04 ` Martin Steigerwald
2018-09-19 20:11 ` Hans van Kranenburg
2018-09-19 20:30 ` Nikolay Borisov
2018-09-20 0:55 ` Qu Wenruo
2018-09-20 7:46 ` Duncan
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=e0f21dace16885d1bd615dd723235d57@virtall.com \
--to=tch@virtall.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).