public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Niemayer <niemayer@isg.de>
To: linux-xfs@oss.sgi.com
Subject: Re: observed significant performance improvement using "delaylog" in
Date: Thu, 12 Aug 2010 23:46:43 +0200	[thread overview]
Message-ID: <i41q43$6td$1@dough.gmane.org> (raw)
In-Reply-To: <201008122105.35787@zmi.at>

On 08/12/2010 09:05 PM, Michael Monnerie wrote:
> On Donnerstag, 12. August 2010 Khelben Blackstaff wrote:
>> Here is my post with the results of the benchmark.
>> http://lordkhelben.wordpress.com/2010/07/08/xfs-delayed-logging/
>
> Wow, BTRFS rocks.

Be sure to measure your specific use-case before jumping
to conclusions.

With our application, for example, Btrfs performed exceptionally
bad - about 4 times(!) as slow as XFS.

Then again, there are some use-cases where even older
file-systems like reiser3 excel (e.g. storing files for
cyrus imapd).


> But I'm stunned that XFS is that much slower than ext4 in many tests.

Again, it all depends on the use-case. For us, ext4
performs good (when used with all kinds of performance-enhancing,
safety-reducing mount-options), but not as good as XFS.

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.


One thing, I guess, is for sure: Every file-system will require
continued development to stay competitive.

SSDs, for example, are just beginning to get used appropriately
by modern file-systems. There's plenty of opportunity left to
optimize for them.

And once that is done, there may be yet another storage-technology
available (PRAM? Racetrack?), that benefits from specific strategies.

So the competition will stay open... :-)

Regards,

Peter Niemayer


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-08-12 21:46 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 [this message]
2010-08-13  9:56     ` Stan Hoeppner
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='i41q43$6td$1@dough.gmane.org' \
    --to=niemayer@isg.de \
    --cc=linux-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