public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Török Edwin" <edwintorok@gmail.com>
To: "Török Edwin" <edwintorok@gmail.com>, xfs@oss.sgi.com
Subject: Re: Speed of rm compared to reiserfs (slow)
Date: Fri, 26 Sep 2008 10:41:27 +0300	[thread overview]
Message-ID: <48DC9227.6060908@gmail.com> (raw)
In-Reply-To: <20080925235453.GF27997@disturbed>

On 2008-09-26 02:54, Dave Chinner wrote:
> On Thu, Sep 25, 2008 at 11:16:35AM +0300, Török Edwin wrote:
>   
>> On 2008-09-25 03:27, Dave Chinner wrote:
>>     
>>> On Wed, Sep 24, 2008 at 11:43:13AM +0300, Török Edwin wrote:
>>>       
>> 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?
>>     
>
> Buy more disks. ;)
>
> XFS is not really optimised for single disk, metadata intensive,
> small file workloads.

I have 6 disks, in raid10 :)

md4 : active raid10 sda3[0] sdf3[5] sdc3[4] sde3[3] sdd3[2] sdb3[1]
      2159617728 blocks 64K chunks 2 near-copies [6/6] [UUUUUU]

--- Logical volume ---
  LV Name                /dev/vg-all/lv-var
  VG Name                vg-all
  LV UUID                CQHPts-K3OE-9kWV-hg7q-328i-RP0i-Dew94c
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                1.27 TB
  Current LE             332800
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1

  --- Segments ---
  Logical extent 0 to 332799:
    Type                linear
    Physical volume     /dev/md4
    Physical extents    25600 to 358399

>  It scales by being able to keep lots of disks
> busy at the same time. Those algorithms don't map to single disk
> configs as efficiently as a filesystem that was specifically
> designed for optimal performance for these workloads (like
> reiserfs). We're working on making it better, but that takes time....

I see.
Well the read performance is very good as I said in my initial email ;)

Thanks,
--Edwin

  reply	other threads:[~2008-09-26  7:40 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
2008-09-25 23:54     ` Dave Chinner
2008-09-26  7:41       ` Török Edwin [this message]
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=48DC9227.6060908@gmail.com \
    --to=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