summaryrefslogtreecommitdiff
path: root/chat/gaim/Makefile
diff options
context:
space:
mode:
authoragc <agc@pkgsrc.org>2003-07-17 15:13:19 +0000
committeragc <agc@pkgsrc.org>2003-07-17 15:13:19 +0000
commit00b4fa03c623e15039cce41d18f797f42b68c00b (patch)
tree85d3afd8d1495fa1cbb8193e29111d8031a7dc2d /chat/gaim/Makefile
parent1031625be7b13cede75aad14657d962f524ef29d (diff)
downloadpkgsrc-00b4fa03c623e15039cce41d18f797f42b68c00b.tar.gz
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.
Diffstat (limited to 'chat/gaim/Makefile')
0 files changed, 0 insertions, 0 deletions