From: Steve Bergman <steve@rueb.com>
To: linux-kernel@vger.kernel.org, steve@rueb.com
Subject: Disk hardware caching, performance, and journalling
Date: Sat, 24 Nov 2001 12:36:18 -0600 [thread overview]
Message-ID: <3BFFE8A2.1010708@rueb.com> (raw)
Hi,
I made a couple of discoveries today which were surprising to me:
1. Disk hardware caching defaults to ON. (hdparm -W1 /dev/hda)
2. It makes a *big* difference in write performance.
I had always thought that the default was off. I also always assumed
that a small cache behind a large (OS) cache would make no difference.
Here are my results with bonnie under kernel 2.4.14 on a reiserfs with a
maxtor Diamond max+ 60GB udma100 drive:
Write caching on:
-------Sequential Output-------- ---Sequential Input-- --Random--
-Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks---
Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU
/sec %CPU
256 12618 97.1 38027 36.3 9647 6.9 11250 73.6 31832
12.1 200.9 1.2
Write caching off:
-------Sequential Output-------- ---Sequential Input-- --Random--
-Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks---
Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU
/sec %CPU
256 9917 76.3 12280 11.2 5159 3.5 9934 65.3 33056
14.1 203.9 1.4
Note that block writes are over 3 times faster with caching on.
So what are the implications here for journalling? Do I have to turn
off caching and suffer a huge performance hit?
-Steve Bergman
next reply other threads:[~2001-11-24 18:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 18:36 Steve Bergman [this message]
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
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=3BFFE8A2.1010708@rueb.com \
--to=steve@rueb.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®