public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: Stan Hoeppner <stan@hardwarefreak.com>, xfs@oss.sgi.com
Subject: Re: observed significant performance improvement using "delaylog" in
Date: Fri, 13 Aug 2010 08:29:07 -0400	[thread overview]
Message-ID: <20100813122907.GA14650@infradead.org> (raw)
In-Reply-To: <201008131235.45050@zmi.at>

On Fri, Aug 13, 2010 at 12:35:44PM +0200, Michael Monnerie wrote:
> On Freitag, 13. August 2010 Stan Hoeppner wrote:
> > Some benchmark results maybe worth a look:
> > http://btrfs.boxacle.net/repository/raid/2.6.35-rc5/2.6.35-rc5/
>  
> Thanks - it would have been great to see xfs with delaylog in that 
> comparison, but the graphs are very very nice.
> 
> XFS seems performing better the more threads there are, just in "large 
> file random reads" it's the slowest - why this?

Any idea who is doing these runs?  Once we figure out what that large
file random reads loads is I'm sure we could fix it soon.  And asking
him/her to add -o delaylog would also be good.

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

  reply	other threads:[~2010-08-13 12:28 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
2010-08-13 10:35       ` Michael Monnerie
2010-08-13 12:29         ` Christoph Hellwig [this message]
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=20100813122907.GA14650@infradead.org \
    --to=hch@infradead.org \
    --cc=michael.monnerie@is.it-management.at \
    --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