From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: habanero@us.ibm.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: Journal FS Comparison on IOzone (was Netbench)
Date: Wed, 29 Aug 2001 09:39:27 -0700 [thread overview]
Message-ID: <3B8D1ABF.4ED398DA@osdlab.org> (raw)
In-Reply-To: <3B8A6122.3C784F2D@us.ibm.com> <3B8A9070.AD43D0E7@osdlab.org> <200108271929.OAA23048@popmail.austin.ibm.com>
Andrew Theurer wrote:
>
> On Monday 27 August 2001 01:24 pm, Randy.Dunlap wrote:
> > Hi,
> >
> > I am doing some similar FS comparisons, but using IOzone
> > (www.iozone.org) instead of Netbench.
> >
> > Some preliminary (mostly raw) data are available at:
> > http://www.osdlab.org/reports/journal_fs/
> > (updated today).
> >
> > I am using a Linux 2.4.7 on a 4-way VA Linux system.
> > It has 4 GB of RAM, but I have limited it to 256 MB in
> > accordance with IOzone run rules.
> >
> > However, I suspect that this causes IOzone to measure disk
> > subsystem or PCI bus performance more than it does FS performance.
> > Any comments on this?
>
> Randy,
>
> You are definitly exceeding what the kernel will cache and writing to disk on
> some tests. I guess it depends on what is more important to you. I think
> both are valid things to test, and you may want to try not limiting memory to
> get just FS performace in memory for large files. However, writing to disk
> is important, especially for things like bounce-buffer. Did you have himem
> support in your kernel? If so, did you have a bounce-buffer elimination
> patch as well?
Hi-
Sorry about the delay in responding.
I'm interested in filesystem performance. I'm not trying to
document IDE vs. SCSI vs. FC performance/price tradeoffs, benefits,
etc.
> Does the storage system/controller have a disk cache? What size?
Good questions, but I'm having trouble finding answers for them.
(hence the delay in responding)
The FC host controller is a QLogic 2200. It is attached to an
IBM FAStT controller/drive array -- one controller with 10
attached drives. I've been looking at the IBM FAStT OS console
interface, but I can't see much cache info there.
There is one item: cache/processor sizes: 88/40 MB
> Also, does IOzone default to num procs=num cpus? I didn't see any options in
> your cmdline for num_procs.
No, IOzone doesn't default to num_processes = num_cpus.
That's a command-line option that I didn't use, although I expect
to do some testing with that option also.
Thanks for your comments.
~Randy
next prev parent reply other threads:[~2001-08-29 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 15:02 Journal Filesystem Comparison on Netbench Andrew Theurer
2001-08-27 18:24 ` Journal FS Comparison on IOzone (was Netbench) Randy.Dunlap
2001-08-27 18:59 ` Brian
2001-08-27 19:28 ` Andrew Theurer
2001-08-29 16:39 ` Randy.Dunlap [this message]
2001-08-30 15:08 ` YAFB: Yet Another Filesystem Bench Yves Rougy
2001-08-27 20:04 ` Journal Filesystem Comparison on Netbench Hans Reiser
2001-08-27 20:29 ` Andrew Theurer
2001-08-27 21:19 ` Randy.Dunlap
2001-08-27 21:41 ` [reiserfs-dev] " Hans Reiser
2001-08-28 10:05 ` Roberto Nibali
2001-08-28 15:28 ` Andrew Theurer
2001-08-28 18:38 ` Andrew Morton
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=3B8D1ABF.4ED398DA@osdlab.org \
--to=rddunlap@osdlab.org \
--cc=habanero@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.