Skip to content

Benchmarking

For the complete documentation index see: llms.txt

All documentation pages available in markdown.

This page describes how to benchmark an Aerospike cluster with the Aerospike Benchmark tool (asbench) and how to check cluster health with asadm. Before benchmarking, verify that the object size, read/write mix, concurrency, and access patterns match your workload.

Use Aerospike Benchmark (asbench) to measure cluster performance and simulate workloads with configurable record structures, access patterns, and latency reporting.

With asbench, you can:

  • Read and write data at a selected read/write ratio.
  • Change client threads and asynchronous command limits to simulate concurrency.
  • Configure object specs to match your record structure.
  • Review periodic latency output and HDR histogram data.

Run

The following command starts the default benchmark against a local cluster and the default test namespace:

Terminal window
asbench --hosts 127.0.0.1 --namespace test

For connection, TLS, workload, and latency options, see Aerospike Benchmark (asbench).

Check your cluster status with asadm

Use asadm to verify cluster health before and after a benchmark run. The info command shows node, namespace, and object information.

Connect to the cluster:

Terminal window
asadm -h 127.0.0.1 -p 3000

At the Admin> prompt, run:

info

Confirm that the cluster size, namespace state, migrations, and stop-writes values match your expected test conditions. Complete asadm documentation is available in the Tools documentation.

Feedback

Was this page helpful?

What type of feedback are you giving?

What would you like us to know?

+Capture screenshot

Can we reach out to you?