All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Steve Bergman <steve@rueb.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Disk hardware caching, performance, and journalling
Date: Sun, 25 Nov 2001 22:19:26 +1300	[thread overview]
Message-ID: <20011125221926.B9672@weta.f00f.org> (raw)
In-Reply-To: <3BFFE8A2.1010708@rueb.com>
In-Reply-To: <3BFFE8A2.1010708@rueb.com>

On Sat, Nov 24, 2001 at 12:36:18PM -0600, Steve Bergman wrote:

    1. Disk hardware caching defaults to ON. (hdparm -W1 /dev/hda)
    2. It makes a *big* difference in write performance.

I depends on the drive, my IDE drives do default to on, my SCSI drives
do not.

The difference in write performance doesn't seem to be a problem other
that in contrived situations (eg. streaming 5G of data to disk takes
the same amount of time either way, but untar something then 'sync' is
faster with the drive caching).

It also depends of your filesystems to some extent and the operations
being performed [1].

    So what are the implications here for journalling?  Do I have to
    turn off caching and suffer a huge performance hit?

Yes.  I do this on workstations and it doesn't seem to hurt in
practice (only in benchmarks).

I can't comment on your bonnie++ results and I have no idea how well
they reflect reality (I assume to a large extent they try to though).




  --cw

[1] XFS rm -rf some_large_dir bites with drive-caching off for example.

      parent reply	other threads:[~2001-11-25  9:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-24 18:36 Disk hardware caching, performance, and journalling Steve Bergman
2001-11-24 19:08 ` Andrew Morton
2001-11-24 19:39   ` Florian Weimer
2001-11-24 21:57   ` Phil Howard
2001-11-25  9:22   ` Chris Wedgwood
2001-11-24 19:39 ` Mark Hahn
2001-11-25  9:23   ` Chris Wedgwood
2001-11-25 21:45     ` Kevin P. Fleming
2001-11-25 22:11       ` Chris Wedgwood
2001-11-25 22:29         ` Mark Hahn
2001-11-26  1:10       ` Bernd Eckenfels
2001-11-25  9:19 ` Chris Wedgwood [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=20011125221926.B9672@weta.f00f.org \
    --to=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve@rueb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.