public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: gus3 <musicman529@yahoo.com>
To: xfs@oss.sgi.com, david@fromorbit.com,
	"Török Edwin" <edwintorok@gmail.com>
Subject: Re: Speed of rm compared to reiserfs (slow)
Date: Thu, 25 Sep 2008 02:08:26 -0700 (PDT)	[thread overview]
Message-ID: <284797.30246.qm@web34501.mail.mud.yahoo.com> (raw)
In-Reply-To: <48DB48E3.3020104@gmail.com>

--- On Thu, 9/25/08, Török Edwin <edwintorok@gmail.com> wrote:

> >> I did a test on my box, and indeed the speed of rm
> is order of magnitude
> >> slower compared to reiserfs.
> >> I already use lazy-count, and noatime/nodiratime.
> Write barriers are off
> >> because I run on raid10.
> >>
> >> Is there anything else I can tune to get faster rm
> speed?

Others' suggestions stand, but I have found the best way to speed up a journalled filesystem (of any kind) is with an external journal on a separate controller channel. If your XFS journal is internal, the RAID10 layer creates a longer data path when actions are recorded in the journal, then read from the journal, and finally committed to the main filesystem.

You may also investigate the speed of different elevator algorithms. XFS does best with "noop" or "deadline" in my experience. Most Linux distributions ship with "cfq" as their default elevator, which can clash badly against XFS.

  reply	other threads:[~2008-09-25  9:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24  8:43 Speed of rm compared to reiserfs (slow) Török Edwin
2008-09-25  0:27 ` Dave Chinner
2008-09-25  8:16   ` Török Edwin
2008-09-25  9:08     ` gus3 [this message]
2008-09-25 23:54     ` Dave Chinner
2008-09-26  7:41       ` Török Edwin
2008-09-28 16:34         ` Speed of rm compared to reiserfs (slow) - and switching logdevices Török Edwin
2008-09-28 18:25           ` Eric Sandeen
2008-09-28 19:27             ` Török Edwin

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=284797.30246.qm@web34501.mail.mud.yahoo.com \
    --to=musicman529@yahoo.com \
    --cc=david@fromorbit.com \
    --cc=edwintorok@gmail.com \
    --cc=xfs@oss.sgi.com \
    /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