From: Chris Mason <chris.mason@oracle.com>
To: Bron Gondwana <brong@fastmail.fm>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Poor performance unlinking hard-linked files (repost)
Date: Tue, 16 Nov 2010 08:38:13 -0500 [thread overview]
Message-ID: <1289914577-sup-8535@think> (raw)
In-Reply-To: <20101116125445.GA3229@brong.net>
Excerpts from Bron Gondwana's message of 2010-11-16 07:54:45 -0500:
> Just posting this again more neatly formatted and just the
> 'meat':
>
> a) program creates piles of small temporary files, hard
> links them out to different directories, unlinks the
> originals.
>
> b) filesystem size: ~ 300Gb (backed by hardware RAID5)
>
> c) as the filesystem grows (currently about 30% full)
> the unlink performance becomes horrible. Watching
> iostat, there's a lot of reading going on as well.
>
> Is this expected? Is there anything we can do about it?
> (short of rewrite Cyrus replication)
Hi,
It sounds like the unlink speed is limited by the reading, and the reads
are coming from one of two places. We're either reading to cache cold
block groups or we're reading to find the directory entries.
Could you sysrq-w while the performance is bad? That would narrow it
down.
Josef has the reads for caching block groups fixed, but we'll have to
look hard at the reads for the rest of unlink.
-chris
next prev parent reply other threads:[~2010-11-16 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 3:25 Poor performance unlinking hard-linked files Bron Gondwana
2010-11-16 12:54 ` Poor performance unlinking hard-linked files (repost) Bron Gondwana
2010-11-16 13:38 ` Chris Mason [this message]
2010-11-17 4:11 ` Bron Gondwana
2010-11-17 9:56 ` Bron Gondwana
2010-11-18 15:30 ` Chris Mason
2010-11-18 21:46 ` Bron Gondwana
2010-11-19 14:10 ` Chris Mason
2010-11-19 21:58 ` Bron Gondwana
2010-11-30 9:35 ` Bron Gondwana
2010-11-30 12:49 ` Chris Mason
2010-11-30 23:24 ` Bron Gondwana
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=1289914577-sup-8535@think \
--to=chris.mason@oracle.com \
--cc=brong@fastmail.fm \
--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).