summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2019-05-05 20:04:52 +0000
committerintrigeri <intrigeri@boum.org>2019-05-05 20:04:52 +0000
commit0e3209b2615de48c7542ff9cfecc0516def1008f (patch)
treee1bb66b8400d958eb10effc568632174d6282380
parent581a12d5a6a5526d414de8832745d325b8de29b3 (diff)
Report benchmark results (refs: #15501)
-rw-r--r--wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn6
1 files changed, 4 insertions, 2 deletions
diff --git a/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn b/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
index 847e36d..74457d8 100644
--- a/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
+++ b/wiki/src/blueprint/hardware_for_automated_tests_take3.mdwn
@@ -50,7 +50,9 @@ area:
a replica of our Jenkins setup, also using nested virtualization,
with a poor Internet connection but faster CPU cores
- 26 minutes (including 5 minutes for building the website) on bare metal,
- with a poor Internet connection but a fast (Intel E-2134) CPU
+ with a poor Internet connection but a fast (Intel E-2134) CPU;
+ same in a VM on that machine, i.e. using nested virtualization
+ (only 1 concurrent build).
* Waiting time in queue for ISO build and test jobs is acceptable
most of the time, but too high during peak load periods:
@@ -250,7 +252,7 @@ Cons:
- Left to benchmark:
- Higher density: run 2 Jenkins worker VMs on this node (neither our
build system nor test suite implementation allow running 2 jobs at
- a time on the same system)
+ a time on the same system) and make them busy at the same time.
## Run builds and/or tests in the cloud