On Sun, Sep 30, 2007 at 05:27:03PM -0700, David Miller wrote: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 -
| hooanon05 | [PATCH 67/67] merge aufs |
| Greg Kroah-Hartman | [PATCH 008/196] Chinese: add translation of volatile-considered-harmful.txt |
| monstr | [PATCH 33/52] [microblaze] bug headers files |
| Oliver Pinter | Re: x86: 4kstacks default |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Natalie Protasevich | [BUG] New Kernel Bugs |
