From a636f35e47989633efa912aac6a27c570372bd87 Mon Sep 17 00:00:00 2001
From: Simon Ehrenstein <simon.ehrenstein@gmail.com>
Date: Sun, 9 Aug 2020 23:48:51 +0200
Subject: [PATCH] Update docs

---
 execution/README.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/execution/README.md b/execution/README.md
index af4caaa80..7db6164ec 100644
--- a/execution/README.md
+++ b/execution/README.md
@@ -156,3 +156,11 @@ The `./theodolite.sh` is the entrypoint for all benchmark executions. Is has to
 * `<memory-limit>`: Kubernetes memory limit. Optional. Default `4Gi`.
 * `<commit-interval>`: Kafka Streams' commit interval in milliseconds. Optional. Default `100`.
 * `<duration>`: Duration in minutes subexperiments should be executed for. Optional. Default `5`.
+* `<strategy>`: The benchmarking strategy. Can be set to `default` or `step`. For more details see Section _Benchmarking Strategies_. Default `default`.
+
+### <a name="benchmarking-strategies"></a>Benchmarking Strategies
+There are the following benchmarking strategies:
+
+* `default`: Execute a subexperiment for each combination of the number of replicas (N), and the number of workload intensities (M). The amount of executed subexperiments is N*M.
+* `step`: After each subexperiment, it is checked, whether the application could handle the workload. If the workload could be handled, the workload intensity is increased in the next subexperiment. Otherwise, the workload intensity is kept the same and the number of instances is increased. The amount of executed subexperiments is at most N+M-1.
+
-- 
GitLab