pkgsrc/benchmarks/dbench/distinfo

$NetBSD: distinfo,v 1.11 2008/05/01 13:17:55 obache Exp $

SHA1 (dbench-3.04.tar.gz) = 09d7b647663ddc3e5617956dedd1aa6a4da2d840
RMD160 (dbench-3.04.tar.gz) = 707f396aec21e6c6c79a6b93217e9503356cefea
Size (dbench-3.04.tar.gz) = 2078197 bytes
SHA1 (patch-aa) = 462f50ac9d529d788f165556846df88b8d8765c6
SHA1 (patch-ab) = 8d17f83c86ef9b733f6970454f3321a8afdac600
SHA1 (patch-ac) = b60ff204f1f2a1f30976a8c2a51f19e0633e4bf5
Update dbench to 3.04. Changes is unknown. While here, * install README file mentioned in man page, suggested in PR 38553. * move client.txt to subdir noted in man page * fix directory of those files in man page. 2008-05-01 15:17:55 +02:00			$NetBSD: distinfo,v 1.11 2008/05/01 13:17:55 obache 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
Update dbench to 3.04. Changes is unknown. While here, * install README file mentioned in man page, suggested in PR 38553. * move client.txt to subdir noted in man page * fix directory of those files in man page. 2008-05-01 15:17:55 +02:00			`SHA1 (dbench-3.04.tar.gz) = 09d7b647663ddc3e5617956dedd1aa6a4da2d840`
			`RMD160 (dbench-3.04.tar.gz) = 707f396aec21e6c6c79a6b93217e9503356cefea`
			`Size (dbench-3.04.tar.gz) = 2078197 bytes`
Use O_FSYNC instead of O_SYNC on DragonFly. Disable extattr_get_file on DragonFly, the semantic is different and it isn't very useful in the current form. 2005-11-06 20:39:49 +01:00			`SHA1 (patch-aa) = 462f50ac9d529d788f165556846df88b8d8765c6`
Update dbench to 3.04. Changes is unknown. While here, * install README file mentioned in man page, suggested in PR 38553. * move client.txt to subdir noted in man page * fix directory of those files in man page. 2008-05-01 15:17:55 +02:00			`SHA1 (patch-ab) = 8d17f83c86ef9b733f6970454f3321a8afdac600`
Make this package build on Darwin. getxattr(2) and setxattr(2) on Darwin require additional arguments related to the resource fork attribute. 2006-03-17 00:00:08 +01:00			`SHA1 (patch-ac) = b60ff204f1f2a1f30976a8c2a51f19e0633e4bf5`