From: Andi Kleen <freitag@alancoxonachip.com>
To: llarsh@oracle.com
Cc: linux-kernel@vger.kernel.org, mason@suse.com
Subject: Re: 2x Oracle slowdown from 2.2.16 to 2.4.4
Date: 12 Jul 2001 12:14:16 +0200 [thread overview]
Message-ID: <oup8zhue9on.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0107111530170.2342-100000@llarsh-pc3.us.oracle.com.suse.lists.linux.kernel>
In-Reply-To: Lance Larsh's message of "12 Jul 2001 00:58:14 +0200"
Lance Larsh <llarsh@oracle.com> writes:
>
> I ran lots of iozone tests which illustrated a huge difference in write
> throughput between reiser and ext2. Chris Mason sent me a patch which
> improved the reiser case (removing an unnecessary commit), but it was
> still noticeably slower than ext2. Therefore I would recommend that
> at this time reiser should not be used for Oracle database files.
When I read the 2.4.6 reiserfs code correctly reiserfs does not cause
any transactions for reads/writes to allocated blocks; i.e. you're not extending
the file, you're not filling holes and you're not updating atimes.
My understanding is that this is normally true for Oracle, but probably
not for iozone so it would be better if you benchmarked random writes
to an already allocated file.
The 2.4 page cache is more or less direct write through in this case.
-Andi
next parent reply other threads:[~2001-07-12 10:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0107111530170.2342-100000@llarsh-pc3.us.oracle.com.suse.lists.linux.kernel>
2001-07-12 10:14 ` Andi Kleen [this message]
2001-07-12 14:22 ` 2x Oracle slowdown from 2.2.16 to 2.4.4 Chris Mason
2001-07-12 16:09 ` Lance Larsh
2001-07-11 0:45 Brian Strand
2001-07-11 1:15 ` Andrea Arcangeli
2001-07-11 16:44 ` Brian Strand
2001-07-11 17:08 ` Andrea Arcangeli
2001-07-11 17:23 ` Chris Mason
2001-07-11 23:03 ` Lance Larsh
2001-07-11 23:46 ` Brian Strand
2001-07-12 15:21 ` Lance Larsh
2001-07-12 21:31 ` Hans Reiser
2001-07-12 21:51 ` Chris Mason
2001-07-13 3:00 ` Andrew Morton
2001-07-13 4:17 ` Andrew Morton
2001-07-13 15:36 ` Jeffrey W. Baker
2001-07-13 15:49 ` Andrew Morton
2001-07-16 22:03 ` Stephen C. Tweedie
2001-07-12 0:23 ` Chris Mason
2001-07-12 14:48 ` Lance Larsh
2001-07-12 2:30 ` Andrea Arcangeli
2001-07-12 6:12 ` parviz dey
2001-07-11 2:58 ` Jeff V. Merkey
2001-07-11 15:55 ` Brian Strand
2001-07-11 2:59 ` Jeff V. Merkey
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=oup8zhue9on.fsf@pigdrop.muc.suse.de \
--to=freitag@alancoxonachip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llarsh@oracle.com \
--cc=mason@suse.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