On Sun, Sep 30, 2007 at 05:27:03PM -0700, David Miller wrote:
> From: Valerie Henson <[email protected]>
> 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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
