public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jens Beyer <jens.beyer@1und1.de>
Cc: xfs@oss.sgi.com
Subject: Re: XFS perfomance degradation on growing filesystem size
Date: Tue, 8 Jul 2008 08:06:47 +1000	[thread overview]
Message-ID: <20080707220647.GN29319@disturbed> (raw)
In-Reply-To: <20080707080409.GA18390@webde.de>

On Mon, Jul 07, 2008 at 10:04:09AM +0200, Jens Beyer wrote:
> On Fri, Jul 04, 2008 at 12:59:41AM -0700, Dave Chinner wrote:
> > On Fri, Jul 04, 2008 at 08:41:26AM +0200, Jens Beyer wrote:
> > > 
> > > I have encountered a strange performance problem during some 
> > > hardware evaluation tests: 
> > > 
> > > I am running a benchmark to measure especially random read/write 
> > > I/O on an raid device and found that (under some circumstances) 
> > > the performance of Random Read I/O is inverse proportional to the 
> > > size of the tested XFS filesystem. 
> > > 
> > > In numbers this means that on a 100GB partition I get a throughput 
> > > of ~25 MB/s and on the same hardware at 1TB FS size only 18 MB/s 
> > > (and at 2+ TB like 14 MB/s) (absolute values depend on options, 
> > > kernel version and are for random read i/o at 8k test block size).
> > 
> > Of course - as the filesystem size grows, so does the amount of
> > each disk in use so the average seek distance increases and hence
> > read I/Os take longer.
> 
> But then - why does the rate of ext3 does not decrease and stays at the
> higher value? 

Because XFS spreads the data and metadata across the entire
filesystem, not just a small portion. It's one of the reasons XFS
can make decent use of lots of disks effectively.  Grab seekwatcher
traces from your workload for the different filesystems and you'll
see what I mean....

Cheers,,

Dave.
-- 
Dave Chinner
david@fromorbit.com

      reply	other threads:[~2008-07-07 22:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04  6:41 XFS perfomance degradation on growing filesystem size Jens Beyer
2008-07-04  7:59 ` Dave Chinner
2008-07-07  8:04   ` Jens Beyer
2008-07-07 22:06     ` Dave Chinner [this message]

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=20080707220647.GN29319@disturbed \
    --to=david@fromorbit.com \
    --cc=jens.beyer@1und1.de \
    --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