1DBENCH(1) General Commands Manual DBENCH(1)
2
6 dbench - Measure disk throughput for simulated netbench run
7
9 dbench [options]numclients
10 tbench [options]numclientsserver tbench_srv [options]
11
13 This manual page documents briefly the dbench and tbench benchmarks.
14 This manual page was written for the Debian GNU/Linux distribution
15 because the original program does not have a manual page. However, it
16 has fairly easy to read source code.
17 Netbench is a terrible benchmark, but it's an "industry standard" and
19 it's what is used in the press to rate windows fileservers like Samba
20 and WindowsNT.
21 Given the requirements of running netbench (60 and 150 Windows PCs all
22 on switched fast ethernet and a really grunty server, and a to open up
23 netbench to the masses.
24 Both dbench and tbench read a load description file called client.txt
25 that was derived from a capture of a real netbench run. client.txt is
26 about 25MB and describes the 500 thousand operations that a netbench
27 client does in a typical netbench run. They parse client.txt and use it
28 to produce the same load without having to buy a huge lab.
29 dbench produces only the filesystem load. It does all the same IO calls
30 that the smbd server in Samba would produce when confronted with a net‐
31 bench run. It does no networking calls.
32 tbench produces only the TCP and process load. It does the same socket
33 calls that smbd would do under a netbench load. It does no filesystem
34 calls. The idea behind tbench is to eliminate smbd from the netbench
35 test, as though the smbd code could be made infinately fast.
36
38 The dbench program takes a number, which indicates the number of
39 clients to run simultaneously. It can also take the following options:
40 -c client.txt
42 Use this as the full path name of the client.txt file (the
43 default is /usr/share/dbench/client.txt).
44 -s Use synchronous file IO on all file operations.
46 -t TIME
48 set the runtime of the benchmark in seconds (default 600)
49 -D DIR set the base directory to run the filesystem operations in
51 -x enable xattr support, simulating the xattr operations Samba4
53 would need to perform to run the load
54 -S Use synchronous IO for all directory operations (unlink, rmdir,
56 mkdir and rename).
57 The tbench program takes a number, which indicates the number of
58 clients to run simultaneously, and a server name: tbench_srv
59 should be invoked on that server before invoking tbench. tbench
60 can also take the following options:
61 -c loadfile
63 Use this as the full path name of the client.txt file (the
64 default is /usr/share/dbench/client.txt).
65 -T option[,...]
67 This sets the socket options for the connection to the server.
68 The options are a comma-separated list of one or more of the
69 following: SO_KEEPALIVE, SO_REUSEADDR, SO_BROADCAST, SO_NODELAY,
70 SO_LOWDELAY, SO_THROUGHPUT, SO_SNDBUF=number, SO_RCVBUF=number,
71 SO_SNDLOWAT=number, SO_RCVLOWAT=number, SO_SNDTIMEO=number,and
72 SO_RCVTIMEO=number. See socket(7) for details about these
73 options.
74 The tbench_srv can only take one option: -t option[,...] as
75 documented above.
76
78 /usr/share/doc/dbench/README contains the original README by Andrew
79 Tridgell which accompanies the dbench source.
80
82 This manual page was written by Paul Russell <prussell@alder‐
83 aan.franken.de>, for the Debian GNU/Linux system (but may be used by
84 others).
85 October 15, 2001 DBENCH(1)