Skip to content
Snippets Groups Projects
Commit 877ae5ec authored by Sören Henning's avatar Sören Henning
Browse files

Minor doc fixes

parent aacf038b
No related branches found
No related tags found
2 merge requests!159Re-implementation of Theodolite with Kotlin/Quarkus,!152Adjust Benchmark Definitions for Operator
Pipeline #3915 passed
This commit is part of merge request !152. Comments created here will be created in the context of that merge request.
# Defining a Benchmark
Please note that to simply run a benchmark, it is not required to define one. Theodolite comes with a set of benchmarks, which are ready to be executed. See the Benchmarks and Executions docs page to learn more about our distinction between benchmarks and executions.
* Create a benchmark for operator mode
* Create a benchmark for standalone mode
* Deploy a benchmark
......@@ -12,6 +18,8 @@
## Creating a benchmark for standalone mode
Creating a benchmark in standalone mode is similar to operator mode. However,
......
......@@ -20,7 +20,7 @@ automatically one after another.
## Running Benchmarks with the Theodolite Operator
The general process for running Theodolite benchmarks in standalone mode is as follows:
The general process for running Theodolite benchmarks in operator mode is as follows:
1. Create and deploy a new `Benchmark` resource or deploy one of the already existing ones.
2. Define your benchmark execution as an `Execution` resource and deploy it.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment