Yes thank you everyone, really important improvements !! DJ
On Sun, Jun 16, 2019 at 11:34 PM Zppix <[email protected]> wrote: > 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 < > [email protected]> 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 > > > > [0]: > > > https://integration.wikimedia.org/ci/job/wmf-quibble-core-vendor-mysql-hhvm-docker/lastCompletedBuild/testReport/(root)/ > > [1]: https://phabricator.wikimedia.org/T225184 > > [2]: > https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/515023 > > [3]: > https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Babel/+/514735 > > [4]: https://phabricator.wikimedia.org/T225496 > > [5]: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/513106 > > [6]: https://phabricator.wikimedia.org/T225248 > > [7]: https://phabricator.wikimedia.org/F29585158 > > > > 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 > > [email protected] > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
