summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2016-03-07 12:05:24 +0000
committerintrigeri <intrigeri@boum.org>2016-03-07 12:05:24 +0000
commitc7d59476cc0613831dfae48f95cf77358340d73f (patch)
tree31a56b24206a730dacec27d7a4e72123533ba028
parent3fe4f483adf22ba1ed3efb92dad173e897b0329e (diff)
Draft "Performance improvements on Jenkins".
-rw-r--r--wiki/src/blueprint/SponsorS/reports/2016_02.mdwn21
1 files changed, 19 insertions, 2 deletions
diff --git a/wiki/src/blueprint/SponsorS/reports/2016_02.mdwn b/wiki/src/blueprint/SponsorS/reports/2016_02.mdwn
index e85bb8b..0efacca 100644
--- a/wiki/src/blueprint/SponsorS/reports/2016_02.mdwn
+++ b/wiki/src/blueprint/SponsorS/reports/2016_02.mdwn
@@ -142,8 +142,25 @@ XXX: anonym or intrigeri
- Performance improvements on Jenkins
- XXX: intrigeri (platform optimization: [[!tails_ticket 11175]],
- [[!tails_ticket 11113]])
+ We figured we could probably get some nice test suite performance
+ improvements, on our Jenkins environment, by optimizing the platform
+ itself.
+
+ After an initial round of benchmarking conducted in January, our
+ next action was to give our server more RAM in order to give us more
+ flexibility to evaluate different configuration options. This was
+ done in February, and then we went through a few optimization
+ cycles, identifying bottlenecks and addressing them until we were
+ satisfied ([[!tails_ticket 11175]], [[!tails_ticket 11113]],
+ <https://tails.boum.org/blueprint/hardware_for_automated_tests_take2/#benchmarks>).
+
+ As a result, we have improved our test suite runs throughput, in the
+ worst case scenario, from 3.3 to 8 runs per hour. This gives us room
+ to run more automated tests in that environment, and also shortens
+ the feedback loop for developers, since congestion is now less
+ likely to happen. We will keep an eye on metrics to confirm, in one
+ or two months, that real workloads indeed benefit from
+ these changes.
## B.4. Freezable APT repository