From: John Goerzen <jgoerzen@complete.org>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Extremely slow metadata performance
Date: Thu, 05 Dec 2013 11:52:04 -0600 [thread overview]
Message-ID: <52A0BD44.9030509@complete.org> (raw)
Hello,
I have observed extremely slow metadata performance with btrfs. This may
be a bit of a nightmare scenario; it involves untarring a backup of
1.6TB of backuppc data, which contains millions of hardlinks and much
data, onto USB 2.0 disks.
I have run disk monitoring tools such as dstat while performing these
operations to see what's going on.
The behavior I notice is this:
* When unpacking large files, the USB drives sustain activity in the
20-40 MB/s range, as expected.
* When creating vast numbers of hardlinks instead, the activity is
roughly this:
o Bursts of output from tar due to -v, sometimes corresponding to
reads in the 300KB/s range (I suspect this has
to do with caching)
o Tar blocked for minutes while writes to the disk occur, in the
300-600KB/s range.
This occurs even when nobarrier,noatime are specified as mount options.
I know the disk is capable of far more, because btrfs gets
far more from it when writing large files.
There are two USB drives in this btrfs filesystem: a 1TB and a 2TB
drive. I have tried the raid1, raid0, and single metadata profiles.
Anecdotal evidence suggests that raid1 performs the worst, raid0 the
best, and single somewhere in between. The data is in single mode.
Is this behavior known and expected?
Thanks,
John
next reply other threads:[~2013-12-05 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 17:52 John Goerzen [this message]
2013-12-05 19:39 ` Extremely slow metadata performance Duncan
2013-12-07 9:22 ` Marc MERLIN
2013-12-07 17:10 ` Kai Krakow
2013-12-05 23:41 ` Russell Coker
[not found] ` <5930575.71jgM0vnzg@xev>
2013-12-06 4:48 ` John Goerzen
2013-12-06 14:35 ` John Goerzen
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=52A0BD44.9030509@complete.org \
--to=jgoerzen@complete.org \
--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).