From: Tomasz Chmielewski <tch@virtall.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: dedicated metadata drives?
Date: Fri, 04 Jan 2019 22:25:18 +0900 [thread overview]
Message-ID: <fcdfebdcb0e8d5fd291d08f844274212@virtall.com> (raw)
According to btrfs wiki, some patches have been submitted to support
metadata on different devices than data (i.e. metadata on SSD, data on
HDD):
https://btrfs.wiki.kernel.org/index.php/Project_ideas#Dedicated_metadata_drives
Dedicated metadata drives
Not claimed — submitted — Not in kernel yet
We're able to split data and metadata IO very easily. Metadata tends
to be dominated by seeks and for many applications it makes sense to put
the metadata onto faster SSDs.
This article (almost 2.5 years old) claims one company is already using
either these patches or something similar:
https://lwn.net/Articles/698090/
August 24, 2016
To combat that, he has a set of patches to automatically put the
Btrfs metadata on SSDs. The block layer provides information on whether
the storage is rotational; for now, his patch assumes that if
it is not rotational then it is fast. The patch has made a huge
difference in the latencies and requires less flash storage (e.g. 450GB
for 40TB filesystem) for Facebook's file workload that
consists of a wide variety of file sizes.
Do these patches exist anywhere? I couldn't find them in the list
archive.
Tomasz
next reply other threads:[~2019-01-04 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 13:25 Tomasz Chmielewski [this message]
2019-01-09 2:39 ` dedicated metadata drives? Paul Jones
2019-01-09 13:33 ` Eli V
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=fcdfebdcb0e8d5fd291d08f844274212@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).