Thank you to everyone who has been working on this, I’m sure everyone will appreciate this, and what is to come in the future!

-- Devin “Zppix” CCENT Volunteer Wikimedia Developer Africa Wikimedia Developers Member and Mentor Volunteer Mozilla Support Team Member (SUMO) Quora.com Partner Program Member enwp.org/User:Zppix **Note: I do not work for Wikimedia Foundation, or any of its chapters. I also do not work for Mozilla, or any of its projects. **

On Jun 16, 2019, at 1:07 PM, Amir Sarabadani amir.sarabadani@wikimedia.de wrote:

Hey, In the past couple of weeks, jenkins jobs became considerably slow. There has been some actions to improve it.

• There's the list of slow phpunit tests [0]

** One test in CirrusSearch was taking 1 minutes and 30 seconds, that's fixed and now it takes around 20 seconds [1] ** There was an innocent test that was taking 8.6 seconds because it was sleeping 8.5 seconds of it to make sure the cache is expired, that is fixed as well [2] ** There was a rather slow test in Babel extension. It's cleaned up [3]

• Mediawiki caching in browser tests has changed from database-based cache

to APC cache, dropping ~1200 queries in every jenkins test job. Saving 30 seconds from core CI jobs and more in extensions [4] (It was a really big low-hanging fruit)

• There's a work to separate unit tests and integration tests that beside

other benefits, it saves around 10 seconds of each phpunit job. It got merged but it had to be reverted due to breaking Postgres tests, hopefully will get it fixed and re-merged soon [5]

• There has been several discussions on how to improve performance of

browser tests [6]

🎉🎉🎉This chart sums up the result of the work done so far. Hopefully it'll get even better [7] 🎉🎉🎉

== What you can do? ==

• Please take a look at [0] and see if the extension you are maintaining or

developing has strangely long tests, if so, please fix it.

• Let's get [5] re-merged!
• Please participate at the discussions at [6] about browser tests

Have a lovely day

Amir Sarabadani (he/him) Software engineer

Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Tel. (030) 219 158 26-0 https://wikimedia.de

Unsere Vision ist eine Welt, in der alle Menschen am Wissen der Menschheit teilhaben, es nutzen und mehren können. Helfen Sie uns dabei! https://spenden.wikimedia.de

Wikimedia Deutschland — Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207. _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

On Sun, Jun 16, 2019 at 08:07:02PM +0200, Amir Sarabadani wrote:

In the past couple of weeks, jenkins jobs became considerably slow. There has been some actions to improve it.

Excellent! I'm very glad to hear about these improvements.

Software development is a set of concentric loops, the innermost of which is the tight edit-build-test loop. The loop that expands this to include CI is a little less tight, but its speed is also crucial. The longer the loops, the longer it takes to make any change, so any shortening of loops is highly likely to result in increased productivity.

I'm especially glad to hear there's movement to separate actual unit tests (individual components in the code based tested in isolation from other parts of the code, and from the external world) from integration tests that happen to be implemented using unit test tooling (which is a fine way of implementing them, but they're not unit tests).