-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>dbench</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" title="dbench"><a name="dbench.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>dbench — a benchmark tool</p></div><div class="refsynopsisdiv" title="Synopsis"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">dbench [OPTIONS] <num-procs></code> </p></div><div class="cmdsynopsis"><p><code class="command">dbench</code> [-B --backend=<dbench backend>] [-c --loadfile=<filename>] [-D --directory=<string>] [-F --fsync] [-R --target-rate=<double>] [-s --sync] [-S --sync-dir] [-t --timelimit=<integer>] [-T --tcp-options=<string>] [--run-once] [--fake-io] [--scsi=<scsi-device>] [--server=<hostname>] [--export=<string>] [--protocol=<string>] [--clients-per-process=<integer>] [--trunc-io=<integer>] [--stat-check] [--skip-cleanup] [--per-client-results] [--iscsi-device=<iSCSI URL>] [--iscsi-initiatorname=<iSCSI InitiatorName>] [-? --help] [--usage]</p></div></div><div class="refsect1" title="DESCRIPTION"><a name="id32
6321"></a><h2>DESCRIPTION</h2><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>dbench</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" title="dbench"><a name="dbench.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>dbench — a benchmark tool</p></div><div class="refsynopsisdiv" title="Synopsis"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">dbench [OPTIONS] <num-procs></code> </p></div><div class="cmdsynopsis"><p><code class="command">dbench</code> [-B --backend=<dbench backend>] [-c --loadfile=<filename>] [-D --directory=<string>] [-F --fsync] [-R --target-rate=<double>] [-s --sync] [-S --sync-dir] [-t --timelimit=<integer>] [-T --tcp-options=<string>] [--run-once] [--fake-io] [--scsi=<scsi-device>] [--server=<hostname>] [--export=<string>] [--protocol=<string>] [--clients-per-process=<integer>] [--trunc-io=<integer>] [--stat-check] [--skip-cleanup] [--per-client-results] [--iscsi-device=<iSCSI URL>] [--iscsi-initiatorname=<iSCSI InitiatorName>] [-? --help] [--usage]</p></div></div><div class="refsect1" title="DESCRIPTION"><a name="id32
7222"></a><h2>DESCRIPTION</h2><p>
dbench is a utility to benchmark a system based on client workload
profiles.
- </p></div><div class="refsect1" title="STANDARD OPTIONS"><a name="id32
6332"></a><h2>STANDARD OPTIONS</h2><div class="refsect2" title="-B --backend=<dbench backend>"><a name="id326338"></a><h3>-B --backend=<dbench backend></h3><p>
+ </p></div><div class="refsect1" title="STANDARD OPTIONS"><a name="id32
7232"></a><h2>STANDARD OPTIONS</h2><div class="refsect2" title="-B --backend=<dbench backend>"><a name="id327238"></a><h3>-B --backend=<dbench backend></h3><p>
The backend type specifies which kind of commandset and what kind of
tests that dbench will perform. The backend type specifies which
kind of loadfile that can be used.
</p><p>
There are currently six types of backends : "fileio", "sockio", "nfs", "scsi", "iscsi" and "smb". The default is "fileio" which uses a smbtorture/BENCH-NBENCH style loadfile.
- </p></div><div class="refsect2" title="-c --loadfile=<filename>"><a name="id32
6354"></a><h3>-c --loadfile=<filename></h3><p>
+ </p></div><div class="refsect2" title="-c --loadfile=<filename>"><a name="id32
7254"></a><h3>-c --loadfile=<filename></h3><p>
This specifies the name of the loadfile to use. The loadfile describes
the sequence and timing of operations that dbench will issue.
- </p></div><div class="refsect2" title="-D --directory=<string>"><a name="id32
6364"></a><h3>-D --directory=<string></h3><p>
+ </p></div><div class="refsect2" title="-D --directory=<string>"><a name="id32
7265"></a><h3>-D --directory=<string></h3><p>
This controls which directory that dbench will use as the root for when
running the loadfile. This defaults to "." which refers to the current
directory for the "fileio" and "sockio" backends and the root of the
export for the "nfs" backend.
- </p></div><div class="refsect2" title="-R --target-rate=<double>"><a name="id32
6376"></a><h3>-R --target-rate=<double></h3><p>
+ </p></div><div class="refsect2" title="-R --target-rate=<double>"><a name="id32
7276"></a><h3>-R --target-rate=<double></h3><p>
By default dbench will try to replay the loadfile and keep the same
rate as the original application the loadfile was captured from.
Using this option it is possible to run the load file faster/slower
</p><p>
By setting this limit to something very large, such as 999999.99 you can
effectively tell dbench to "run this loadfile as fast as possible".
- </p></div><div class="refsect2" title="-t --timelimit=<integer>"><a name="id32
6398"></a><h3>-t --timelimit=<integer></h3><p>
+ </p></div><div class="refsect2" title="-t --timelimit=<integer>"><a name="id32
7299"></a><h3>-t --timelimit=<integer></h3><p>
How long to run the test for.
- </p></div><div class="refsect2" title="--run-once"><a name="id32
6407"></a><h3>--run-once</h3><p>
+ </p></div><div class="refsect2" title="--run-once"><a name="id32
7308"></a><h3>--run-once</h3><p>
Only run the loadfile once and stop when the end of the loadfile is
reached.
</p><p>
The default for dbench is to wrap the loadfile when the end is
reached and continue running the loadfile over and over until the
timelimit is reached.
- </p></div><div class="refsect2" title="--clients-per-process=<integer>"><a name="id32
6422"></a><h3>--clients-per-process=<integer></h3><p>
+ </p></div><div class="refsect2" title="--clients-per-process=<integer>"><a name="id32
7322"></a><h3>--clients-per-process=<integer></h3><p>
By default dbench will fork one child process for each client emulated.
Using this option dbench will run multiple emulated clients inside
each process.
This is useful for testing how performance differs between the case
of n processes with one thread of I/O each and one process with n threads
of I/O.
- </p></div><div class="refsect2" title="--skip-cleanup"><a name="id32
6437"></a><h3>--skip-cleanup</h3><p>
+ </p></div><div class="refsect2" title="--skip-cleanup"><a name="id32
7338"></a><h3>--skip-cleanup</h3><p>
Do not cleanup and delete all temporary files in the clients work
directory when the test ends.
- </p></div><div class="refsect2" title="--per-client-results"><a name="id32
6447"></a><h3>--per-client-results</h3><p>
+ </p></div><div class="refsect2" title="--per-client-results"><a name="id32
7348"></a><h3>--per-client-results</h3><p>
When the test is finished print a latency report for each inidvidual
client in addition to the aggregated report over all clients.
- </p></div></div><div class="refsect1" title="FILEIO OPTIONS"><a name="id32
6459"></a><h2>FILEIO OPTIONS</h2><div class="refsect2" title="-F --fsync"><a name="id326464"></a><h3>-F --fsync</h3><p>
+ </p></div></div><div class="refsect1" title="FILEIO OPTIONS"><a name="id32
7359"></a><h2>FILEIO OPTIONS</h2><div class="refsect2" title="-F --fsync"><a name="id327365"></a><h3>-F --fsync</h3><p>
This option only apply to the "fileio" backend.
</p><p>
This will make dbench perform a fsync() to the file after each write
operation.
- </p></div><div class="refsect2" title="-s --sync-open"><a name="id32
6478"></a><h3>-s --sync-open</h3><p>
+ </p></div><div class="refsect2" title="-s --sync-open"><a name="id32
7378"></a><h3>-s --sync-open</h3><p>
This option only apply to the "fileio" backend.
</p><p>
This makes dbench override the loadfile and use O_SYNC for all
file open operations.
- </p></div><div class="refsect2" title="-S --sync-dir"><a name="id32
6492"></a><h3>-S --sync-dir</h3><p>
+ </p></div><div class="refsect2" title="-S --sync-dir"><a name="id32
7391"></a><h3>-S --sync-dir</h3><p>
This option only apply to the "fileio" backend.
</p><p>
Call fsync() on the directory after each "unlink", "rmdir" or "rename"
operation. This emulates how the linux kernel nfs daemon syncs
directories after performing directory modifying operations.
- </p></div><div class="refsect2" title="--fake-io"><a name="id32
6506"></a><h3>--fake-io</h3><p>
+ </p></div><div class="refsect2" title="--fake-io"><a name="id32
7405"></a><h3>--fake-io</h3><p>
This option only apply to the "fileio" backend.
</p><p>
Do not do any file read/write operations at all.
- </p></div><div class="refsect2" title="--stat-check"><a name="id32
6520"></a><h3>--stat-check</h3><p>
+ </p></div><div class="refsect2" title="--stat-check"><a name="id32
7417"></a><h3>--stat-check</h3><p>
This option only apply to the "fileio" backend.
</p><p>
After each create/mkdir/rmdir/rename operation, immediately try to
is correct. I.e. Verify that immediately after we have created an
object that stat() will succeed and that immediately after we have
deleted an object that stat() will fail.
- </p></div></div><div class="refsect1" title="SOCKIO OPTIONS"><a name="id32
6536"></a><h2>SOCKIO OPTIONS</h2><div class="refsect2" title="-T --tcp-options=<string>"><a name="id326542"></a><h3>-T --tcp-options=<string></h3><p>
+ </p></div></div><div class="refsect1" title="SOCKIO OPTIONS"><a name="id32
7433"></a><h2>SOCKIO OPTIONS</h2><div class="refsect2" title="-T --tcp-options=<string>"><a name="id327438"></a><h3>-T --tcp-options=<string></h3><p>
This option only apply to the "sockio" backend.
- </p></div></div><div class="refsect1" title="SMB OPTIONS"><a name="id32
6553"></a><h2>SMB OPTIONS</h2><div class="refsect2" title="--smb-share=//<hostname>/<share>[/<path>]"><a name="id326558"></a><h3>--smb-share=//<hostname>/<share>[/<path>]</h3><p>
+ </p></div></div><div class="refsect1" title="SMB OPTIONS"><a name="id32
7448"></a><h2>SMB OPTIONS</h2><div class="refsect2" title="--smb-share=//<hostname>/<share>[/<path>]"><a name="id327454"></a><h3>--smb-share=//<hostname>/<share>[/<path>]</h3><p>
This option only apply to the "smb" backend.
</p><p>
This option is mandatory when the "smb" backend is used.
This specifies the server and the share to use for the testing. It also contains an optional path to a directory to use.
</p><p>
Example: --smb-share=//MY-SERVER/DATA
- </p></div><div class="refsect2" title="--smb-user=[<domain>/]<user>%<password>"><a name="id32
6580"></a><h3>--smb-user=[<domain>/]<user>%<password></h3><p>
+ </p></div><div class="refsect2" title="--smb-user=[<domain>/]<user>%<password>"><a name="id32
7474"></a><h3>--smb-user=[<domain>/]<user>%<password></h3><p>
This option only apply to the "smb" backend.
</p><p>
This option is mandatory when the "smb" backend is used.
This specifies the username and password to use when authenticationg to the server.
</p><p>
Example: --smb-user=Administrator%Password
- </p></div></div><div class="refsect1" title="NFS OPTIONS"><a name="id32
6603"></a><h2>NFS OPTIONS</h2><div class="refsect2" title="--server=<hostname>"><a name="id326608"></a><h3>--server=<hostname></h3><p>
+ </p></div></div><div class="refsect1" title="NFS OPTIONS"><a name="id32
7495"></a><h2>NFS OPTIONS</h2><div class="refsect2" title="--server=<hostname>"><a name="id327500"></a><h3>--server=<hostname></h3><p>
This option only apply to the "nfs" backend.
</p><p>
This option is mandatory when the "nfs" backend is used.
</p><p>
This specifies the host-name or ip-address of the server to test.
- </p></div><div class="refsect2" title="--export=<string>"><a name="id32
6626"></a><h3>--export=<string></h3><p>
+ </p></div><div class="refsect2" title="--export=<string>"><a name="id32
7516"></a><h3>--export=<string></h3><p>
This option only apply to the "nfs" backend.
</p><p>
This option is mandatory when the "nfs" backend is used.
</p><p>
This specifies the nfs-export on the server to do i/o to.
- </p></div><div class="refsect2" title="--protocol=<string>"><a name="id32
6643"></a><h3>--protocol=<string></h3><p>
+ </p></div><div class="refsect2" title="--protocol=<string>"><a name="id32
7531"></a><h3>--protocol=<string></h3><p>
This option only apply to the "nfs" backend.
</p><p>
This specifies whether "tcp" or "udp" is to be used. Default is "tcp".
- </p></div><div class="refsect2" title="--trunc-io=<integer>"><a name="id32
6656"></a><h3>--trunc-io=<integer></h3><p>
+ </p></div><div class="refsect2" title="--trunc-io=<integer>"><a name="id32
7543"></a><h3>--trunc-io=<integer></h3><p>
This option only apply to the "nfs" backend.
</p><p>
Some NFS server may have limitations on how large READ/WRITE I/Os they
accept preventing some loadfiles from running. Using this option will
override the length specified in the loadfile and make dbench never
issuing any READ/WRITE operations larger than this.
- </p></div></div><div class="refsect1" title="SCSI OPTIONS"><a name="id32
6673"></a><h2>SCSI OPTIONS</h2><div class="refsect2" title="--scsi=<scsi-device>"><a name="id326678"></a><h3>--scsi=<scsi-device></h3><p>
+ </p></div></div><div class="refsect1" title="SCSI OPTIONS"><a name="id32
7559"></a><h2>SCSI OPTIONS</h2><div class="refsect2" title="--scsi=<scsi-device>"><a name="id327564"></a><h3>--scsi=<scsi-device></h3><p>
This option only apply to the "scsi" backend.
</p><p>
This option is mandatory when the "scsi" backend is used.
</p><p>
This specifies the device node of the scsi-device we want to run the loadfile on. Example: --scsi=/dev/sda
- </p></div></div><div class="refsect1" title="iSCSI OPTIONS"><a name="id32
6698"></a><h2>iSCSI OPTIONS</h2><p>
+ </p></div></div><div class="refsect1" title="iSCSI OPTIONS"><a name="id32
7582"></a><h2>iSCSI OPTIONS</h2><p>
Dbench contains a primitive iSCSI initiator, allowing it to perform I/O
to some iSCSI targets.
- </p><div class="refsect2" title="--iscsi-device=<iSCSI URL>"><a name="id32
6708"></a><h3>--iscsi-device=<iSCSI URL></h3><p>
+ </p><div class="refsect2" title="--iscsi-device=<iSCSI URL>"><a name="id32
7592"></a><h3>--iscsi-device=<iSCSI URL></h3><p>
This option only apply to the "iscsi" backend.
</p><p>
This option is mandatory when the "iscsi" backend is used.
</p><p>
This specifies the URL to the target device. URLs are specified as "iscsi://<ip-address>[:<port>]/<target-iqn>/<lun>"
- </p></div><div class="refsect2" title="--iscsi-initiatorname=<iSCSI InitiatorName>"><a name="id32
6726"></a><h3>--iscsi-initiatorname=<iSCSI InitiatorName></h3><p>
+ </p></div><div class="refsect2" title="--iscsi-initiatorname=<iSCSI InitiatorName>"><a name="id32
7609"></a><h3>--iscsi-initiatorname=<iSCSI InitiatorName></h3><p>
This option only apply to the "iscsi" backend.
</p><p>
This option is optional when the "iscsi" backend is used.
</p><p>
This specifies the InitiatorName that dbench will use when connecting to the client.
- </p></div></div><div class="refsect1" title="COPYRIGHT/LICENSE"><a name="id32
6745"></a><h2>COPYRIGHT/LICENSE</h2><div class="literallayout"><p><br>
+ </p></div></div><div class="refsect1" title="COPYRIGHT/LICENSE"><a name="id32
7626"></a><h2>COPYRIGHT/LICENSE</h2><div class="literallayout"><p><br>
Copyright (C) Andrew Tridgell 2008<br>
Copyright (C) Ronnie Sahlberg 2008<br>
<br>
git.samba.org / sahlberg / dbench.git / commitdiff