linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Clayton <andrew@digital-domain.net>
To: David Chinner <dgc@sgi.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: XFS regression?
Date: Thu, 11 Oct 2007 10:05:03 +0100	[thread overview]
Message-ID: <20071011100503.1e4544c5@zeus.pccl.info> (raw)
In-Reply-To: <20071011010139.GT995458@sgi.com>

On Thu, 11 Oct 2007 11:01:39 +1000, David Chinner wrote:

 
> Latencies are an order of magnitude lower at 60-70ms because the disks
> have less deep queues. This is expected - deep queues and multiple
> outstanding I/Os are the enemy of single I/O latency....
> 
> If I remount with barriers enabled, the latency at nr_requests=128
> goes up to a consistent 2.2s. Not surprising, we're flushing the drive
> cache very regularly now and it points to the create or truncate
> transaction having to pushing log buffers to disk. The latency remains
> at 70-80ms at nr_requests=4.

Thanks for the info. I did try fiddling nr_requests but I made it
bigger. I'll try with it lower.
 
> > It seems this problem was introduced between 2.6.18 and 2.6.19. 
> 
> When the new SATA driver infrastructure was introduced. Do you have
> NCQ enabled on more recent kernels and not on 2.6.18? If so, try
> disabling it and see if the problem goes away....

Unfortunately the drives in the file server don't support NCQ. Not sure
if it's supported in the machine I was testing on (it's certainly a few
years old).
 
> > The other thing I've found is that if I do the dd to an ext3 fs (on
> > the same disk at least) while running the test in the XFS fs then I
> > also see the latencies.
> 
> So it's almost certainly pointing at an elevator or driver change, not
> an XFS change.

OK, though it doesn't seem to effect ext3. I'm going to run a git
bisect to see what it comes up with.

> Cheers,
> 
> dave.

Cheers,

Andrew

  reply	other threads:[~2007-10-11  9:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 14:27 XFS regression? Andrew Clayton
2007-10-11  1:01 ` David Chinner
2007-10-11  9:05   ` Andrew Clayton [this message]
2007-10-11 14:15   ` Andrew Clayton
2007-10-11 21:53     ` David Chinner
2007-10-12  0:26       ` David Chinner
2007-10-12 11:36         ` Andrew Clayton
2007-10-12 13:28           ` Andrew Clayton
     [not found]           ` <cc7060690710130635u2a85bc28we36b344c0987b691@mail.gmail.com>
2007-10-14 23:09             ` David Chinner
2007-10-15  9:58               ` Bhagi rathi
2007-10-15 11:57                 ` David Chinner
2007-10-14 23:19           ` David 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=20071011100503.1e4544c5@zeus.pccl.info \
    --to=andrew@digital-domain.net \
    --cc=dgc@sgi.com \
    --cc=linux-fsdevel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).