Today we celebrate two numbers: 25% lower latency for ATS backend requests at the p75, and up to 1000X reduction of ATS disk read latency at the p999.
Deploying HTTP/2 support to the Wikimedia CDN significantly changed how browsers negotiate and transfer data during the page load process. We found regressions in performance during the transition and are sharing the lessons we learned.
We built an efficient sampling profiler for PHP. It runs continually in production on live requests, and generates trace logs and flame graphs.
Preview popups are common and requires careful scripting and styling; they can generate useful learning about performance as a reference for other front-end tasks.
The story of how we decided to commission the implementation of Paint Timing API, a feature that lets us observe web performance from an end-user perspective. This web browser feature tells us at what point in time content started to appear on the screen for a visitor.
We have been collecting microbenchmark scores for over a year. This lets us see the long-term evolution of our audience as a whole. The information gives us an idea of how fast device/operating system/browser environments improve on their own.
For FOSDEM 2020, the Wikimedia Performance Team organized a Web Performance devroom. In this post, they share their experience.
WikimediaDebug is a set of tools for debugging and profiling MediaWiki web requests in a production environment. WikimediaDebug can be used through the accompanying browser extension, or from the command-line. This post highlights changes we made to WikimediaDebug over the past year, and explains more generally how its capabilities work.
We’re taking part in the ongoing Event Timing Chrome origin trial, in order to experiment with that API early and give feedback to its designers.