pkgsrc/benchmarks/dbench/distinfo

$NetBSD: distinfo,v 1.2 2003/09/19 18:08:14 wiz Exp $

SHA1 (dbench-1.3.tar.gz) = b46f72ac0a81acf7a0f368e20e5d83ee3932a35a
Size (dbench-1.3.tar.gz) = 266746 bytes
SHA1 (patch-aa) = 1c34848d3ce3294a1ae228243ff6fcae8a874826
SHA1 (patch-ab) = 63d2fd91fcd1e282179ba10c9d6ae06e89f6b945
Make compile on Solaris. From Jonathan Perkin in PR 22858. 2003-09-19 20:08:14 +02:00			$NetBSD: distinfo,v 1.2 2003/09/19 18:08:14 wiz Exp $
Initial import of dbench-1.3 into the NetBSD Packages Collection. Taken from the dbench README file: Netbench is a terrible benchmark, but it's an "industry standard" and it's what is used in the press to rate windows fileservers like Samba and WindowsNT. In order for the development methodologies of the open source community to work we need to be able to run this benchmark in an environment that a bunch of us have access to. We need the source to the benchmark so we can see what it does. We need to be able to split it into pieces to look for individual bottlenecks. In short, we need to open up netbench to the masses. To do this I have written three tools, dbench, tbench and smbtorture. All three read a load description file called client.txt that was derived from a network sniffer dump of a real netbench run. client.txt is about 4MB and describes the 90 thousand operations that a netbench client does in a typical netbench run. They parse client.txt and use it to produce the same load without having to buy a huge lab. They can simulate any number of simultaneous clients. 2003-07-17 17:11:44 +02:00
			`SHA1 (dbench-1.3.tar.gz) = b46f72ac0a81acf7a0f368e20e5d83ee3932a35a`
			`Size (dbench-1.3.tar.gz) = 266746 bytes`
			`SHA1 (patch-aa) = 1c34848d3ce3294a1ae228243ff6fcae8a874826`
Make compile on Solaris. From Jonathan Perkin in PR 22858. 2003-09-19 20:08:14 +02:00			`SHA1 (patch-ab) = 63d2fd91fcd1e282179ba10c9d6ae06e89f6b945`