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, 30 Nov 2010 07:49:26 -0500 [thread overview]
Message-ID: <1291121299-sup-9081@think> (raw)
In-Reply-To: <20101130093510.GB3622@brong.net>
Excerpts from Bron Gondwana's message of 2010-11-30 04:35:10 -0500:
> On Sat, Nov 20, 2010 at 08:58:10AM +1100, Bron Gondwana wrote:
> > On Fri, Nov 19, 2010 at 09:10:08AM -0500, Chris Mason wrote:
> > > Excerpts from Bron Gondwana's message of 2010-11-18 16:46:31 -0500:
> > > > On Thu, Nov 18, 2010 at 10:30:47AM -0500, Chris Mason wrote:
> > > > > Ok, we're mixing unlinks and fsyncs. If it fsyncing directories too?
> > > >
> > > > Nup. I'm pretty sure it doesn't, just files. Yes - there will certainly
> > > > be fsyncs going on as well - Cyrus is very careful to fsync everything it
> > > > cares about at the file level, but all it does with directories is mkdir
> > > > them if they don't exist.
> > >
> > > Could you double check this one please? fsyncing the directory is a ton
> > > more expensive, I just want to make sure it isn't part of the workload.
> > >
> > > Otherwise it looks like we're seeking to read in the inode and unlink
> > > it. One possibility is that we're not giving the elevator enough clues
> > > about the IO being synchronous.
> > >
> > > Are you using cfq or deadline? I bet we can improve the latencies using
> > > READ_SYNC.
> >
> > I'm using deadline.
> >
> > All I'm seeing is the fsyncs on the files. And some unnecessary mkdir
> > calls that I can probably remove, and an unneccary truncate on the
> > quota file.
>
> Do you have any suggestsions for what I could try? You mentioned READ_SYNC
> above. We now have one working partition on this machine, but it took longer
> to set up than most, and I'm not sure how it will cope with 7 more of them
> (which is my next project - compare to the historical performance of this
> box first with reiserfs and then with ext4!)
Let me work up a patch that does READ_SYNC calls for the metadata reads,
and I'll try to model this here a little. We should be able to improve
things.
-chris
next prev parent reply other threads:[~2010-11-30 12:49 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
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 [this message]
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=1291121299-sup-9081@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.