mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: XFS write speed drop
Date: Wed, 24 May 2006 08:22:19 +1000	[thread overview]
Message-ID: <20060524082218.A267844@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0605231517330.25086@yvahk01.tjqt.qr>; from jengelh@linux01.gwdg.de on Tue, May 23, 2006 at 03:23:31PM +0200

On Tue, May 23, 2006 at 03:23:31PM +0200, Jan Engelhardt wrote:
> >> CASE 1: Copying from one disk to another
> >> ========================================
> >> Copying a compiled 2.6.17-rc4 tree; 306907 KB in 28566 files in 2090
> >> directories.
> >
> >OK, we can call this a metadata intensive workload - lots of small
> >files, lots of creates.  Barriers will hurt the most here, as we'd
> >already have been log I/O bound most likely, and I'd expect barriers
> >to only slow that further.
> >
> Yes and the most important thing is that someone made -o barrier the 
> default and did not notice. Someone else? :-D

Not sure what you're trying to say here.  Yes, barriers are on
by default now if the hardware supports them, yes, they will
slow things down relative to write-cache-without-barriers, and
yes we all knew that ... its not the case that someone "did not
notice" or forgot about something.  There is no doubt that this
is the right thing to be doing by default - there's no way that
I can tell from inside XFS in the kernel that you have a UPS. ;)

cheers.

-- 
Nathan

  reply	other threads:[~2006-05-23 22:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  9:34 Jan Engelhardt
2006-05-22  0:53 ` Nathan Scott
2006-05-22 12:21   ` Jan Engelhardt
2006-05-22 22:43     ` Nathan Scott
2006-05-23 13:23       ` Jan Engelhardt
2006-05-23 22:22         ` Nathan Scott [this message]
2006-05-23 23:17           ` Nathan Scott
2006-05-24  7:16             ` Jeremy Higdon
2006-05-26  7:20         ` Helge Hafting
2006-05-26  8:51           ` Jan Engelhardt
2006-05-26 21:06             ` Bernd Eckenfels
2006-05-23  1:26     ` 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=20060524082218.A267844@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®