-
Notifications
You must be signed in to change notification settings - Fork 12
Home
The Aerospike benchmark tool is used to benchmark the performance of an Aerospike server cluster.
The benchmark tool has the following features
- Raw histogram latency recording
- HDR histogram latency recording
- Workload stages, which can emulate real-world usage patterns
- Enhanced object-spec to allow for complex record structures
For a full list of usage options, see usage.
Supported OS's:
- Linux
Before building, you need to have a local copy of the Aerospike C Client and to have built it. After this, set the environment variable CLIENTREPO
to point to the directory containing the built C client.
Additional external dependencies:
- libyaml
- libev, libuv, or libevent, if an event library is used
To build the benchmark tool, run:
make [EVENT_LIB=libev|libuv|libevent]
with EVENT_LIB
matching the event library used when the C client was compiled, if one was used (it is necessary to build with an event library to use async commands). If an event library is defined, it must be installed separately. Event libraries usually install into /usr/local/lib
. Most operating systems do not search /usr/local/lib
by default. Therefore, the following LD_LIBRARY_PATH
setting may be necessary:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
Now, the benchmark executable will be located at target/benchmark
.
To run the unit tests, call
make test [EVENT_LIB=libev|libuv|libevent]
To generate coverage data for the unit tests, run
make coverage [EVENT_LIB=libev|libuv|libevent]
note: this will rerun the tests.
To view coverage data in the console, run
make report