|In a MediaWiki-based project I'm working on I'm getting many of these
kinds of exceptions: [DBPerformance] Expectation (writes <= 0) by
MediaWiki::main not met (actual: 8) |
|I've read up on the Database transactions article in mediawiki.org and
can see that to remove the exceptions we'd need to conform to some very
specific criteria for all our db write, which is quite a problem for
this particular project.
My question is, are these criteria ever likely to be enforced in future
MW versions, or will they always just be warnings to help guide
performance improvements?
|||
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting this week **Wednesday 3-4 pm UTC**
on #wikimedia-tech.
Questions can be asked in English and Persian!
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about Mediawiki, gadgets,
tools and more! This can be anything from "how to get started" over "who
would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
--
Raz Shuty
Engineering Manager
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
https://wikimedia.de
Imagine a world, in which every single human being can freely share in the
sum of all knowledge. That‘s our commitment.
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.
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…
[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.
Hello folks,
I am Rammanoj, a Google Summer of Code 2019 student for Wikimedia. As part
of the program, I am developing a tool to track developer activity on three
different platforms: Gerrit, Phabricator and Github. Potential users of
this tool will be event organizers, especially scholarship committee
reviewers who need developer contribution statistics while reviewing
applications for Wikimedia events and juggle between different platforms
like Github, Gerrit, Phabricator to view developer activity for deciding on
an applicant.
As a first step, I’ve developed some mockups that explain the proposed
workflow of the tool: https://meta.wikimedia.org/wiki/Contraband#Mockups.
It would be helpful if you could provide me with feedback to continue
further and develop the tool. Please leave your feedback/comments/questions
on the talk page: https://meta.wikimedia.org/wiki/Talk:Contraband.
You can also keep an eye on the technical updates on Phabricator:
https://phabricator.wikimedia.org/T220254.
Thanks & Regards,
Rammanoj
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting this week **Wednesday 3-4 pm UTC**
on #wikimedia-tech.
Questions can be asked in English and German!
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about Mediawiki, gadgets,
tools and more! This can be anything from "how to get started" over "who
would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
--
Raz Shuty
Engineering Manager
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
https://wikimedia.de
Imagine a world, in which every single human being can freely share in the
sum of all knowledge. That‘s our commitment.
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.
MediaWiki core will soon have a REST API.
Some details of the route handler interface are in an RFC which is now
in its last call period:
https://phabricator.wikimedia.org/T221177
If you have any problems with this interface, please tell us as soon
as possible.
There is an associated Gerrit topic branch:
https://gerrit.wikimedia.org/r/q/topic:2019/rest
Several of the changes are almost ready to merge. We're not merging
the entry point (rest.php) just yet, that is still marked WIP.
-- Tim Starling
Hello all,
If you watch the deployment calendar[0] closely you may have noticed a
change recently regarding the individuals listed next to each SWAT
deploy[1] window.
The short version:
* We have removed all Release Engineering team members names from the
list of SWAT deployers.
* Release Engineering team members are still around and available on an
as needed/backup basis.
* Release Engineering team members are still around to respond to any
issues that arise, of course.
* Also, Release Engineering would love to train more individuals on any
engineering team to self-serve their own SWAT deploys. Please contact
me if you'd like to explore next steps.
This is a relatively minor change to reflect the growing reality of how
SWAT deploy windows happen now.
I would also like to take this opportunity to thank all of our current
and past SWAT deployers; thank you for helping get fixes out to our
users quickly and safely.
Best,
Greg
[0] https://wikitech.wikimedia.org/wiki/Deployments
[1] https://wikitech.wikimedia.org/wiki/SWAT_deploys
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
