From: Benjamin LaHaise <bcrl@redhat.com>
To: Abhishek Nayani <abhi@kernelnewbies.org>
Cc: linux-mm@kvack.org
Subject: Re: Benchmarking Tool
Date: Thu, 4 Jul 2002 13:06:31 -0400 [thread overview]
Message-ID: <20020704130631.B21370@redhat.com> (raw)
In-Reply-To: <20020703060446.GA2560@SandStorm.net>; from abhi@kernelnewbies.org on Wed, Jul 03, 2002 at 11:34:46AM +0530
On Wed, Jul 03, 2002 at 11:34:46AM +0530, Abhishek Nayani wrote:
> There was a discussion about the current benchmarking tools being
> not suitable or sufficient for testing the performance of the Linux VMs.
> I am interested in writing one and would like to have your opinions on
> the matter. I would like to know what is missing in the current set of
> tools (lmbench, dbench..) and what is required.
dbench essentially produces a random number for "performance", as it
is overly dependent on small changes in timing, available memory and
execution patterns. lmbench doesn't really test the vm at all. What
is needed are a series of tests that represent the kinds of loads
that various Linux users run. This includes:
- software development
- scientific apps
- desktop
- various server workloads
Most of the time results are presented, they tend to be lacking in some
areas -- much of the high end work being done on >8GB systems tends not
to rerun tests on small systems to make sure behaviour isn't badly
affected. Of the cases listed above, the desktop workload is probably
the most badly represented with current tests.
>From a few of the discussions at OLS, it became apparent that more
important than the actual benchmarking tools is the collection of the
results. Common tests, like compiling the kernel, are useful metrics
for noticing changes in kernel behaviour if all other aspects of the
test environment are held constant, but only if we have a set of data
to compare the results against.
-ben
--
"You will be reincarnated as a toad; and you will be much happier."
--
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:[~2002-07-04 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 6:04 Abhishek Nayani
2002-07-04 17:06 ` Benjamin LaHaise [this message]
2002-07-04 18:49 ` Rik van Riel
2002-07-05 5:52 ` Abhishek Nayani
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=20020704130631.B21370@redhat.com \
--to=bcrl@redhat.com \
--cc=abhi@kernelnewbies.org \
--cc=linux-mm@kvack.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