public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: T?r?k Edwin <edwintorok@gmail.com>,
	xfs-masters@oss.sgi.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: XFS internal error (memory corruption)
Date: Wed, 6 Jul 2011 17:22:21 +1000	[thread overview]
Message-ID: <20110706072221.GZ1026@dastard> (raw)
In-Reply-To: <20110706070756.GA25800@infradead.org>

On Wed, Jul 06, 2011 at 03:07:56AM -0400, Christoph Hellwig wrote:
> On Wed, Jul 06, 2011 at 02:04:03PM +1000, Dave Chinner wrote:
> > > Although is there supposed to be a performance benefit from having
> > > a separate log disk with XFS?
> > 
> > There used to be. Now everyone just uses delayed logging, which is
> > far faster and more scalable that even using an external log.
> 
> Even with delayed logging external logs are a huge benefit if you
> hit the log hard, e.g. for fsync intensive workloads.  E.g. when
> using fs_mark in fsync mode it gives speedups over 100% for the
> setups I've tested.  You'll see similar speedups for NFS server
> loads that are log force heavy as well.

Unless you have a good sized chunk of BBWC in front of your disks,
in which case internal logs are just as fast. In fact, internal logs
can are often faster in this case because an internal log on a 12
disk RAID6 array can sink a whole log more bandwidth than an external
log on a 2-disk RAID0 mirror.....

At least, that's what my hardware tells me. ;)

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2011-07-06  7:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05  6:03 XFS internal error (memory corruption) Török Edwin
2011-07-05 13:09 ` Dave Chinner
2011-07-05 13:38   ` Török Edwin
2011-07-06  4:04     ` Dave Chinner
2011-07-06  7:07       ` Christoph Hellwig
2011-07-06  7:22         ` Dave Chinner [this message]
2011-07-06  8:05           ` Christoph Hellwig

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=20110706072221.GZ1026@dastard \
    --to=david@fromorbit.com \
    --cc=edwintorok@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs-masters@oss.sgi.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