From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: Many-metadata performance still at a loss
Date: Thu, 10 Mar 2011 09:51:00 -0600 [thread overview]
Message-ID: <4D78F364.5000000@hardwarefreak.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1103101507120.5379@obet.zrqbmnf.qr>
Jan Engelhardt put forth on 3/10/2011 8:14 AM:
> Hi,
>
>
> Between 2.6.33 and 2.6.37 there was a lot of interesting announcements
> with regards to XFS performance. However, now that I booted into
> 2.6.37.2, I still see the metadata slowness from earlier.
> (Basically `time (tar -xf linux-2.6.37.tar.gz; sync)` - ext4 gets the
> job done in like 15-20 seconds, xfs is still syncing after 11 minutes.)
>
> Was there something I missed?
Yes. You have to add "delaylog" to your mount options to enable the
metadata performance enhancement. It won't be the default setting until
2.6.39.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-03-10 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 14:14 Many-metadata performance still at a loss Jan Engelhardt
2011-03-10 15:51 ` Stan Hoeppner [this message]
2011-03-11 1:10 ` Dave Chinner
2011-03-11 1:56 ` Jan Engelhardt
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=4D78F364.5000000@hardwarefreak.com \
--to=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