Skip to content
Snippets Groups Projects
Commit 3cf4d249 authored by Simon Ehrenstein's avatar Simon Ehrenstein
Browse files

Update docs

parent 99f085c1
No related branches found
No related tags found
No related merge requests found
...@@ -156,3 +156,11 @@ The `./theodolite.sh` is the entrypoint for all benchmark executions. Is has to ...@@ -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`. * `<memory-limit>`: Kubernetes memory limit. Optional. Default `4Gi`.
* `<commit-interval>`: Kafka Streams' commit interval in milliseconds. Optional. Default `100`. * `<commit-interval>`: Kafka Streams' commit interval in milliseconds. Optional. Default `100`.
* `<duration>`: Duration in minutes subexperiments should be executed for. Optional. Default `5`. * `<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.
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