public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Török Edwin" <edwintorok@gmail.com>
To: xfs@oss.sgi.com, david@fromorbit.com
Subject: Re: Speed of rm compared to reiserfs (slow)
Date: Thu, 25 Sep 2008 11:16:35 +0300	[thread overview]
Message-ID: <48DB48E3.3020104@gmail.com> (raw)
In-Reply-To: <20080925002724.GA27997@disturbed>

On 2008-09-25 03:27, Dave Chinner wrote:
> On Wed, Sep 24, 2008 at 11:43:13AM +0300, Török Edwin wrote:
>   
>> Hi,
>>
>> I am happily using xfs for /var, /usr and /, and I am very pleased with
>> the read speed.
>> I've just recommended xfs to a friend, and he complained about the speed
>> of rm.
>>
>> 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?
>>     
>
> mount -o logbsize=262144 <dev> <mtpt>
>   

I've added it to my mount options, also tried logbufs=8 (but that didn't
make much difference).

>   
>> # mount | grep var
>> /dev/mapper/vg--all-lv--var on /var type xfs (rw,noatime,nodiratime)
>>     
>
> BTW, noatime implies nodiratime - you don't ned to specify both.
>
>   
>> tmpfs                 2.0G   12K  2.0G   1% /lib/init/rw
>> udev                   10M  188K  9.9M   2% /dev
>> tmpfs                 2.0G     0  2.0G   0% /dev/shm
>> /dev/mapper/vg--all-lv--usr
>>                       100G  5.3G   95G   6% /usr
>> /dev/mapper/vg--all-lv--var
>>                       1.3T  230G  1.1T  18% /var
>>     
>
> At 1.1T, you probably want to use inode64 for /var. The different
> allocation strategy of inode32 can be substantially slower than
> inode64.
>
>   

Thanks for the suggestions, the time for rm has improved a bit, but is
still slower than reiserfs:

time rm -rf gcc

real    1m18.818s
user    0m0.156s
sys     0m11.777s

Is there anything else I can try to make it faster?

Best regards,
--Edwin

  reply	other threads:[~2008-09-25  8:15 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 [this message]
2008-09-25  9:08     ` gus3
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=48DB48E3.3020104@gmail.com \
    --to=edwintorok@gmail.com \
    --cc=david@fromorbit.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