Draft "Performance improvements on Jenkins".

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