From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: observed significant performance improvement using "delaylog" in
Date: Fri, 13 Aug 2010 04:56:26 -0500 [thread overview]
Message-ID: <4C6516CA.2010602@hardwarefreak.com> (raw)
In-Reply-To: <i41q43$6td$1@dough.gmane.org>
Peter Niemayer put forth on 8/12/2010 4:46 PM:
> To me, as of today, XFS' big strength is performing good to
> excellent (while not always better than all other file-systems)
> in many use-cases - without worries about instability or immaturity.
+1 But don't forget the excellent tool set which I think is a little better
than those of the other filesystems. XFS has the only functional/reliable
online defrag tool AFAIK. The only 'missing' feature compared to the other
FSes is filesystem shrink ability, but for the majority of XFS users, I'm
guessing this isn't an issue as data sets are always growing.
Some benchmark results maybe worth a look:
http://btrfs.boxacle.net/repository/raid/2.6.35-rc5/2.6.35-rc5/
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-13 9:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 10:46 observed significant performance improvement using "delaylog" in Khelben Blackstaff
2010-08-12 19:05 ` Michael Monnerie
2010-08-12 21:46 ` Peter Niemayer
2010-08-13 9:56 ` Stan Hoeppner [this message]
2010-08-13 10:35 ` Michael Monnerie
2010-08-13 12:29 ` Christoph Hellwig
2010-08-13 14:13 ` Dave Chinner
2010-08-13 20:42 ` Eric Sandeen
2010-08-14 11:28 ` Martin Steigerwald
2010-08-16 0:30 ` Steven Pratt
2010-08-16 1:03 ` Dave Chinner
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=4C6516CA.2010602@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