From 010bd6b8771d699ae5229f43c6f984bddbcb2ad4 Mon Sep 17 00:00:00 2001 From: Raul Sevilla Date: Tue, 9 Aug 2022 17:21:11 +0200 Subject: [PATCH] Dropping the number of clients in the large-scale and small-scale scenarios Fixes: https://github.com/cloud-bulldozer/e2e-benchmarking/issues/451 Signed-off-by: Raul Sevilla --- workloads/router-perf-v2/README.md | 8 ++++---- workloads/router-perf-v2/common.sh | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/workloads/router-perf-v2/README.md b/workloads/router-perf-v2/README.md index f4824c21..c3f837ff 100644 --- a/workloads/router-perf-v2/README.md +++ b/workloads/router-perf-v2/README.md @@ -45,11 +45,11 @@ It's possible to tune the default configuration through environment variables. T | KUBE_BURNER_RELEASE_URL | Kube-burner binary URL | `https://github.com/cloud-bulldozer/kube-burner/releases/download/v0.16/kube-burner-0.16-Linux-x86_64.tar.gz` | | LARGE_SCALE_THRESHOLD | Number of worker nodes required to consider a large scale scenario | `24` | | SMALL_SCALE_ROUTES | Number of routes of each termination to create in the small scale scenario | `100` | -| SMALL_SCALE_CLIENTS | Threads/route to use in the small scale scenario | `1 40 200` | -| SMALL_SCALE_CLIENTS_MIX | Threads/route to use in the small scale scenario with mix termination | `1 20 80` | +| SMALL_SCALE_CLIENTS | Threads/route to use in the small scale scenario | `1 100` | +| SMALL_SCALE_CLIENTS_MIX | Threads/route to use in the small scale scenario with mix termination | `1 50` | | LARGE_SCALE_ROUTES | Number of routes of each termination to create in the large scale scenario | `500` | -| LARGE_SCALE_CLIENTS | Threads/route to use in the large scale scenario | `1 20 80` | -| LARGE_SCALE_CLIENTS_MIX | Threads/route to use in the large scale scenario with mix termination | `1 10 20` | +| LARGE_SCALE_CLIENTS | Threads/route to use in the large scale scenario | `1 20` | +| LARGE_SCALE_CLIENTS_MIX | Threads/route to use in the large scale scenario with mix termination | `1 10` | | DEPLOYMENT_REPLICAS | Number of pod replicas per deployment | `1` | | TLS_REUSE | Reuse TLS session | `true` | | SAMPLES | Number of samples to perform of each test | `2` | diff --git a/workloads/router-perf-v2/common.sh b/workloads/router-perf-v2/common.sh index 16bdb760..3d83ff5a 100644 --- a/workloads/router-perf-v2/common.sh +++ b/workloads/router-perf-v2/common.sh @@ -10,13 +10,13 @@ get_scenario(){ if [[ ${NUM_NODES} -ge ${LARGE_SCALE_THRESHOLD} ]]; then log "Large scale scenario detected: #workers >= ${LARGE_SCALE_THRESHOLD}" export NUMBER_OF_ROUTES=${LARGE_SCALE_ROUTES:-500} - CLIENTS=${LARGE_SCALE_CLIENTS:-"1 20 80"} - CLIENTS_MIX=${LARGE_SCALE_CLIENTS_MIX:-"1 10 20"} + CLIENTS=${LARGE_SCALE_CLIENTS:-"1 20"} + CLIENTS_MIX=${LARGE_SCALE_CLIENTS_MIX:-"1 10"} else log "Small scale scenario detected: #workers < ${LARGE_SCALE_THRESHOLD}" export NUMBER_OF_ROUTES=${SMALL_SCALE_ROUTES:-100} - CLIENTS=${SMALL_SCALE_CLIENTS:-"1 40 200"} - CLIENTS_MIX=${SMALL_SCALE_CLIENTS_MIX:-"1 20 80"} + CLIENTS=${SMALL_SCALE_CLIENTS:-"1 100"} + CLIENTS_MIX=${SMALL_SCALE_CLIENTS_MIX:-"1 50"} fi }