Difficulty: Beginner
Estimated Time: 15 minutes

Effective testing will require you to benchmark your own workload with NoSQLBench!

In this scenario, we'll learn how to:

  • Build a custom workload
  • Run the workload successfully
  • Do some workload trouble shooting

NoSQLBench can show you how your workload will perform. Let's get started!

Check out our datastax.com/dev site, where you can find many more resources to help you succeed with Apache Cassandra™.

ver 0.007

In this scenario, we learned how to:

  • Build a custom workload
  • Run the workload successfully
  • Do some workload trouble shooting

Of course, we've only scratched the surface. Here's a link for a deeper dive.

Customizing Workloads in NoSQLBench

Step 1 of 5

Extract a Workload

The benchmarking workloads we have run in previous scenarios were all pre-packaged. In this scenario, we'll build our own workload.

Before we start, let's make sure Cassandra is running.

nodetool status

It's usually easiest to modify an existing workload. We can list the pre-packaged workloads with this command.

./nb --list-workloads

Then we can extract a workload like this.

./nb --copy cql-iot

Briefly, inspect the extracted file.

Please click to proceed: cql-iot.yaml

Like any unfamiliar yaml file, these can be a bit overwhelming at first glance, but we'll walk you through it. By the end of this scenario, you'll be comfortable with the basics!

You can execute this workload with the following.

./nb ./cql-iot

This may run for a while. Feel free to stop the benchmark using # Ctrl+C.

You may have noticed that running the benchmark can be a bit uneventful. Let's run the benchmark again and have NoSQLBench print out progress every second so we know what's going on.

./nb ./cql-iot --progress console:1s

Once again, feel free to stop the benchmark whenever you feel like it # Ctrl+C.

Since this is our first introduction to workload configuration, we'll create some stripped-down files to emphasize the important parts. We'll use these stripped-down files instead of the one we extracted, but when we are done, you should be able to understand the file we extracted.

You now know how to extract a workload file. Next, we'll learn about the parts of the file.