From: Benjamin Schindler <bschindler@inf.ethz.ch>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs performance problem
Date: Wed, 27 Apr 2011 01:23:23 +0200 [thread overview]
Message-ID: <4DB753EB.6080904@inf.ethz.ch> (raw)
In-Reply-To: <4DB74331.3030804@hardwarefreak.com>
Hi
On 27.04.2011 00:12, Stan Hoeppner wrote:
> Benjamin Schindler put forth on 4/26/2011 2:44 PM:
>> Hi
>>
>> Since upgrading to newer kernels I have serious problems with xfs
>> performance on my root fs.
>> It runs on a software raid 0 with 2 disks. On the same two disks, there
>> are two more partitions running a software raid-1 with ext3. On the ext3
>> system, I have no issue, so I assume the drives are fine.
>> But on the xfs filesystem, extracting a linux kernel archive takes 5
>> minutes or more, running ldconfig similarily long. The harddrives are
>> sata-2.
>> I'm running gentoo linux with kernel 2.6.38-gentoo-r1. I'm attaching the
>> kernel config but I guess more info is needed - just let me know what is
>> needed.
>
> The kernel config isn't the problem. You haven't enabled the delayed
> logging feature. Add 'delaylog' to your fstab mount options for XFS
> devices, remount (or reboot if necessary) and it should decrease the run
> time of kernel tar extractions between 10x and 100x.
Thanks for the hint. I remounted the root filesystem with delaylog.
Even though it improves the situation, it doesn't feel like the
performance is where it used to be on may be 2.6.32 or so. Removing a
lot of files for example is still slow. Removing a kernel source tree
(partial extraction, aborted tar process after it took too long):
metis portage # time rm -rf sources
real 4m40.294s
user 0m0.059s
sys 0m1.468s
That's abnormal right?
metis portage # mount | grep root
/dev/root on / type xfs (rw,noatime,delaylog)
>
> Also, slap yourself in the forehead at least 3 times for running your
> root filesystem on RAID 0. That's akin to riding a motorcycle, naked,
> in a blizzard, down a steep, winding, ice covered mountain road with no
> guard rails and a 3000 ft drop. ;)
>
I don't care if the system gets nuked as long as my user data is
retained (raid 1) so I certainly won't slap myself. Systems can be
reinstalled, user data cannot ;)
Cheers
Benjamin
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-04-26 23:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 19:44 xfs performance problem Benjamin Schindler
2011-04-26 22:12 ` Stan Hoeppner
2011-04-26 23:23 ` Benjamin Schindler [this message]
2011-04-26 23:59 ` Benjamin Schindler
2011-04-29 15:00 ` Peter Grandi
2011-04-30 20:36 ` Michael Monnerie
2011-05-01 8:49 ` Dave Chinner
2011-05-01 14:38 ` Peter Grandi
2011-05-01 15:08 ` Peter Grandi
2011-05-01 15:32 ` Michael Monnerie
2011-05-01 17:04 ` Peter Grandi
2011-05-02 2:50 ` Dave Chinner
2011-05-02 20:10 ` Emmanuel Florac
2011-05-01 13:33 ` Peter Grandi
2011-05-01 16:32 ` Peter Grandi
2011-04-27 7:55 ` Michael Weissenbacher
2011-04-27 8:09 ` Benjamin Schindler
2011-04-27 2:35 ` Dave Chinner
2011-04-29 16:27 ` Martin Steigerwald
2011-05-01 8:52 ` Dave Chinner
2011-05-01 16:55 ` Christoph Hellwig
2011-05-01 18:24 ` Markus Trippelsdorf
2011-05-02 10:14 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2011-04-29 16:28 Martin Steigerwald
2011-04-29 19:51 ` Peter Grandi
2011-05-01 16:56 ` Benjamin Schindler
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=4DB753EB.6080904@inf.ethz.ch \
--to=bschindler@inf.ethz.ch \
--cc=stan@hardwarefreak.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