From cf60fdb8c2f4dc005e9828f405c956cc3cd995c8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=B6ren=20Henning?= <soeren.henning@email.uni-kiel.de>
Date: Thu, 16 Dec 2021 16:30:18 +0100
Subject: [PATCH] Some cleanup
---
docs/misc.md | 8 --------
docs/running-benchmarks.md | 4 +---
2 files changed, 1 insertion(+), 11 deletions(-)
delete mode 100644 docs/misc.md
diff --git a/docs/misc.md b/docs/misc.md
deleted file mode 100644
index 011061fac..000000000
--- a/docs/misc.md
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Some additional hints
-
-### Use results-access Sidecar
-
-```sh
-kubectl cp $(kubectl get pod -l app=theodolite -o jsonpath="{.items[0].metadata.name}"):/results . -c results-access
-```
\ No newline at end of file
diff --git a/docs/running-benchmarks.md b/docs/running-benchmarks.md
index 8f8ee87cf..eda817d28 100644
--- a/docs/running-benchmarks.md
+++ b/docs/running-benchmarks.md
@@ -10,7 +10,7 @@ Running scalability benchmarks with Theodolite involves the following steps:
1. [Deploying a benchmark to Kubernetes](#deploying-a-benchmark)
1. [Creating an execution](#creating-an-execution), which describes the experimental setup for running the benchmark
-1. [Accessing Benchmark Results](#accessing-benchmark-results)
+1. [Accessing benchmark results](#accessing-benchmark-results)
## Deploying a Benchmark
@@ -122,8 +122,6 @@ kubectl describe execution <execution-name>
## Accessing Benchmark Results
-<!-- TODO more specific -->
-
Theodolite stores the results of benchmark executions in CSV files, whose names are starting with `exp<id>_...`. These files can be read and analyzed by Theodolite's analysis notebooks.
If [persisting results](installation#persisting-results) is enabled in Theodolite's installation, the result files are stored in a PersistentVolume. Depending on the cluster setup or Theodolite's configuration, the content of these volumes can usually be mounted into your host system in some way or accessed via your cloud provider.
--
GitLab