From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Nick Piggin'" <nickpiggin@yahoo.com.au>,
"Arjan van de Ven" <arjan@infradead.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: kernel performance update - 2.6.14-rc3
Date: Thu, 6 Oct 2005 11:36:47 -0700 [thread overview]
Message-ID: <200510061836.j96Iamg19185@unix-os.sc.intel.com> (raw)
In-Reply-To: <4344F6A4.2070707@yahoo.com.au>
Nick Piggin wrote on Thursday, October 06, 2005 3:04 AM
> Arjan van de Ven wrote:
> >>dbench is catching some attention. We just ran it with default
> >>parameter. I don't think default parameter is the right one to use
> >>on some of our configurations. For example, it shows +100% improvement
> >
> > never ever consider dbench a serious benchmark; the thing is you can
> > make dbench a lot better very easy; just make the kernel run one thread
> > at a time until completion. dbench really gives very variable results,
> > but it is not really possible to say if +100% or -100% is an improvement
> > or a degredation for real life. So please just don't run it, or at least
> > don't interpret the results in a "higher is better" way.
> >
>
> As a disk IO performance benchmark you are absolutely right.
>
> Some people like using it to test VM scalability and throughput
> if it is being used on tmpfs. In that case the results are
> generally more stable.
Thank you for the suggestion, we will look into the options. I agree here
as well, and I also don't consider dbench as a serious disk I/O performance
benchmark. There are other workloads that we ran (IOzone, aiostress, and my
favorite "industry standard database workload") which covers disk I/O side
pretty well.
- Ken
next prev parent reply other threads:[~2005-10-06 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 21:15 Chen, Kenneth W
2005-10-06 6:16 ` Arjan van de Ven
2005-10-06 10:04 ` Nick Piggin
2005-10-06 18:36 ` Chen, Kenneth W [this message]
2005-10-06 19:24 ` Sonny Rao
2005-10-06 19:32 ` Chen, Kenneth W
2005-10-06 10:32 ` Andi Kleen
2005-10-08 0:49 Jon Burgess
2005-10-08 1:38 ` Chen, Kenneth W
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=200510061836.j96Iamg19185@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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®