public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Peter Niemayer <niemayer@isg.de>
Cc: linux-xfs@oss.sgi.com
Subject: Re: observed significant performance improvement using "delaylog" in a real-world application
Date: Wed, 11 Aug 2010 10:08:54 +1000	[thread overview]
Message-ID: <20100811000854.GL26402@dastard> (raw)
In-Reply-To: <i3rt4t$46c$1@dough.gmane.org>

On Tue, Aug 10, 2010 at 06:01:33PM +0200, Peter Niemayer wrote:
> Hi all,
> 
> we use XFS for a very I/O-intensive, in-house developed real-time
> database application, and whenever we see new or significantly
> changed file-systems becoming available, we run a benchmark using
> this application on a conserved, fixed real-world data set.
> 
> I'm pleased to state that using the experimental "delaylog" mount
> option (in vanilla linux-2.6.35) we measured a 17% performance
> increase
> for our benchmark scenario. (Other mount-options in use both before
> and after the "delaylog" option: noatime,nodiratime,nobarrier)

That's great to hear. One thing that you might want to try to
further improve performance is the logbsize=262144 option as well.
That will help flush log IO faster by doing less IOs.

Also, if your workload is doing lots of fsync calls, then the
optimisations I posted a few days ago should also help improve
delaylog throughput.

> That's a lot given that XFS was the fastest performing file-system
> for this application already.
> 
> It's also a promising result regarding stability, as several other
> tests (using e.g. reiser4 or ceph) in the past led to crashes in the
> same benchmark scenario.

That's definitely encouraging. ;)

> So thanks to all contributing developers for this significant optimization!

And thanks for the feedback.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2010-08-11  0:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 16:01 observed significant performance improvement using "delaylog" in a real-world application Peter Niemayer
2010-08-11  0:08 ` Dave Chinner [this message]
2010-08-11 18:08   ` Peter Niemayer
2010-08-11  8:03 ` Michael Monnerie
2010-08-11  9:45   ` Peter Niemayer
2010-08-11 12:28     ` Michael Monnerie
2010-08-11 17:01       ` Peter Niemayer
2010-08-11 22:31         ` Michael Monnerie
2010-08-11 23:44         ` 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=20100811000854.GL26402@dastard \
    --to=david@fromorbit.com \
    --cc=linux-xfs@oss.sgi.com \
    --cc=niemayer@isg.de \
    /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