summaryrefslogtreecommitdiff
path: root/benchmarks/dbench
AgeCommit message (Collapse)AuthorFilesLines
2016-02-25Use OPSYSVARS.jperkin1-6/+2
2015-11-03Add SHA512 digests for distfiles for benchmarks categoryagc1-1/+2
Problems found with existing distfile for superpi: distfiles/super_pi-20030927/super_pi.tar.gz No changes were made to the superpi/distinfo file. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail. distfiles/eagle-lin32-7.4.0.run
2015-02-08Fix build on SunOS.fhajny2-1/+19
2014-12-12(upstream) update 3.04 to 4.0, changes unknown.mef5-17/+56
(pkgsrc) - Add comment on patches picked from cvs log - Add ${LDFLAGS} on patch-ab for Makefile.in
2014-10-09Remove pkgviews: don't set PKG_INSTALLATION_TYPES in Makefiles.wiz1-3/+1
2012-09-11"user-destdir" is default these daysasau1-2/+1
2012-01-23Remove chunk that was added for 1.6.2 compatibility, but affects thewiz3-19/+5
run-time. Noted by yamt@ in PR 45866. Bump PKGREVISION.
2009-07-08user-destdir supportjoerg1-3/+7
2009-06-14Remove @dirrm entries from PLISTsjoerg1-3/+1
2008-05-01Update dbench to 3.04.obache4-30/+36
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.
2006-03-16Make this package build on Darwin. getxattr(2) and setxattr(2) on Darwinminskim2-5/+34
require additional arguments related to the resource fork attribute.
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2005-11-06Use O_FSYNC instead of O_SYNC on DragonFly. Disable extattr_get_filejoerg3-7/+25
on DragonFly, the semantic is different and it isn't very useful in the current form.
2005-10-10Explicitly specify to Makefile.in the directory on which the manpagesxtraeme3-4/+25
will be installed, otherwise as --mandir now defaults to ${PREFIX}/${PKGMANDIR}, they won't be installed into the correct location. Bump PKGREVISION.
2005-09-25Added a chunk to patch-aa that comments out unnecessary code (statvfs). Nowrillig3-6/+22
the package builds on NetBSD-1.6.2. Bumped PKGREVISION.
2005-07-12Changes 3.03:adam4-57/+14
* Many improvements
2005-03-25Make this package build on Darwin.minskim2-1/+17
- Include sys/aio.h to use O_SYNC. - Use fsync(2) instead of fdatasync(2), which is unavailable on Darwin.
2005-02-22Add RMD160 digests in addition to the SHA1 ones.agc1-1/+2
2004-11-10Changes 2.1:adam5-50/+27
* unknown
2004-10-28Update MASTER_SITES.wiz1-2/+2
2004-07-30Enable pkgviews installation.minskim1-1/+5
2004-01-20Move WRKSRC definition away from the first paragraph in a Makefile.agc1-2/+3
2003-09-19Make compile on Solaris. From Jonathan Perkin in PR 22858.wiz3-10/+35
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-07-17Initial import of dbench-1.3 into the NetBSD Packages Collection.agc6-0/+92
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.