From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: "Randy.Dunlap" <rddunlap@osdlab.org>
Cc: Theodore Tso <tytso@mit.edu>, Andrew Morton <akpm@zip.com.au>,
Daniel Phillips <phillips@bonn-fries.net>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-mm@kvack.org, Rik van Riel <riel@conectiva.com.br>,
Mike Galbraith <mikeg@wen-online.de>,
Steven Cole <elenstev@mesatop.com>,
Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
Subject: Re: 2.4.8-pre1 and dbench -20% throughput
Date: 30 Jul 2001 21:39:22 +0200 [thread overview]
Message-ID: <87lml69pg5.fsf@atlas.iskon.hr> (raw)
In-Reply-To: <3B657A6E.2487127F@osdlab.org> ("Randy.Dunlap"'s message of "Mon, 30 Jul 2001 08:17:02 -0700")
"Randy.Dunlap" <rddunlap@osdlab.org> writes:
> Theodore Tso wrote:
> >
> > On Sun, Jul 29, 2001 at 11:41:50AM +1000, Andrew Morton wrote:
> >
> > > It would be very useful to have a standardised and very carefully
> > > chosen set of tests which we could use for evaluating fs and kernel
> > > performance. I'm not aware of anything suitable, really. It would
> > > have to be a whole bunch of datapoints sprinkled throughout a
> > > multidimesional space. That's what we do at present, but it's ad-hoc.
> >
> > All the gripes about dbench/netbench aside, one good thing about them
> > is that they hit the filesystem with a large number of operations in
> > parallel, which is what a fileserver under heavy load will see.
> > Benchmarks like Andrew and Bonnie tend to have a much more serialized
> > pattern of filesystem access.
>
> Is iozone (using threads) any better at this?
> We are currently using iozone.
>
> And where can I find Zlatko's xmm program that Mike mentioned?
>
http://linux.inet.hr/
--
Zlatko
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-07-30 19:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200107272112.f6RLC3d28206@maila.telia.com>
[not found] ` <0107280034050V.00285@starship>
2001-07-27 23:43 ` Roger Larsson
2001-07-28 1:11 ` Daniel Phillips
2001-07-28 3:18 ` Daniel Phillips
2001-07-28 13:40 ` Marcelo Tosatti
2001-07-28 20:13 ` Daniel Phillips
2001-07-28 20:26 ` Linus Torvalds
2001-07-29 14:10 ` Daniel Phillips
2001-07-29 14:48 ` Rik van Riel
2001-07-29 15:34 ` Daniel Phillips
2001-07-29 15:31 ` Mike Galbraith
2001-07-29 16:05 ` Linus Torvalds
2001-07-29 20:19 ` Hugh Dickins
2001-07-29 20:25 ` Rik van Riel
2001-07-29 20:44 ` Hugh Dickins
2001-07-29 21:20 ` Daniel Phillips
2001-07-29 21:51 ` Hugh Dickins
2001-07-29 23:23 ` Rik van Riel
2001-07-31 7:30 ` Kai Henningsen
2001-07-31 14:13 ` Daniel Phillips
2001-07-31 17:37 ` Jonathan Morton
2001-07-29 1:41 ` Andrew Morton
2001-07-29 14:39 ` Daniel Phillips
2001-07-30 3:19 ` Theodore Tso
2001-07-30 15:17 ` Randy.Dunlap
2001-07-30 16:41 ` Theodore Tso
2001-07-30 17:52 ` Mike Galbraith
2001-07-30 19:39 ` Zlatko Calusic [this message]
2001-07-29 17:48 ` Steven Cole
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=87lml69pg5.fsf@atlas.iskon.hr \
--to=zlatko.calusic@iskon.hr \
--cc=akpm@zip.com.au \
--cc=elenstev@mesatop.com \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=mikeg@wen-online.de \
--cc=phillips@bonn-fries.net \
--cc=rddunlap@osdlab.org \
--cc=riel@conectiva.com.br \
--cc=roger.larsson@skelleftea.mail.telia.com \
--cc=tytso@mit.edu \
/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