linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Valerie Henson <val@nmt.edu>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	rrbranco@br.ibm.com, twichell@us.ibm.com, ycai@us.ibm.com
Subject: Re: [ANNOUNCE] ebizzy 0.2 released
Date: Thu, 4 Oct 2007 14:42:01 -0600	[thread overview]
Message-ID: <20071004204201.GB6090@rainbow> (raw)
In-Reply-To: <20070930.172703.79041329.davem@davemloft.net>

On Sun, Sep 30, 2007 at 05:27:03PM -0700, David Miller wrote:
> From: Valerie Henson <val@nmt.edu>
> Date: Wed, 22 Aug 2007 19:06:26 -0600
> 
> > ebizzy is designed to generate a workload resembling common web
> > application server workloads.
> 
> I downloaded this only to be basically disappointed.
> 
> Any program which claims to generate workloads "resembling common web
> application server workloads", and yet does zero network activity and
> absolutely nothing with sockets is so far disconnected from reality
> that I truly question how useful it really is even in the context it
> was designed for.
> 
> Please describe this program differently, "a threaded cpu eater", "a
> threaded memory scanner", "a threaded hash lookup", or something
> suitably matching what it really does.
> 
> I'm sure there are at least 10 or even more programs in LTP that one
> could run under "time" and get the same exact functionality.

You're right, that part of the description is misleading. (I've even
had people ask me if it's a file systems benchmark!)

Ebizzy is based on a real web application server and does do things
that are fairly common in such applications (multithreaded memory
allocation and memory access), but it ignores networking for two
reasons: the network stack was not the bottleneck for this workload,
the VM was, and really good network benchmarks already exist. :)
ebizzy is not useful to networking (or file systems) developer, but it
has been used to improve malloc() behavior in glibc and to test VMA
handling optimizations.

In general, I try to make the source of a benchmark clear because it's
so tempting to optimize for completely artificial benchmarks.  The
trick is to do this without misleading the reader (or breaking my NDA).

ebizzy
------

ebizzy is a workload that stresses memory allocation and the virtual
memory subsystem.  It was initially written to model the local
computation portion of a web application server running a large
internet commerce site.  ebizzy is highly threaded, has a large
in-memory working set with poor locality, and allocates and
deallocates memory frequently.  When running most efficiently, ebizzy
will max out the CPU.  When running inefficiently, it will be blocked
much of the time.

-VAL

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-10-04 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23  1:06 [ANNOUNCE] ebizzy 0.2 released Valerie Henson
2007-10-01  0:27 ` David Miller, Valerie Henson
2007-10-04 20:42   ` Valerie Henson [this message]
2007-10-04 21:00     ` David Miller, Valerie Henson

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=20071004204201.GB6090@rainbow \
    --to=val@nmt.edu \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rrbranco@br.ibm.com \
    --cc=twichell@us.ibm.com \
    --cc=ycai@us.ibm.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;
as well as URLs for NNTP newsgroup(s).