Wikimedia Performance Team

As the Wikimedia Foundation’s Performance Team, we want to create value for readers and editors by making it possible to retrieve and render content at the speed of thought, from anywhere in the world, on the broadest range of devices and connection profiles.

Focus
Outreach. Our team strives to develop a culture of performance first in the movement. Through communication, embedding ourselves in the product lifecycle and training, we want to make performance a prime consideration in technological and product developments across the movement.

Monitoring. By developing better tooling, designing better metrics, automatically tracking regressions, all in a way that can be reused by anyone, we want to monitor the right metrics and discover issues that can sometimes be hard to detect.

Improvement. Some performance gains require a very high level of expertise and complex work to happen before they are possible. We undertake large projects, often on our legacy code base, that can yield important performance gains in the long run.

Knowledge. We are the movement's reference on all things performance, which requires keeping up with rapid changes in technology across our entire stack. In order to disseminate correct information in our outreach, we aim to build the most comprehensive knowledge base about performance.

Current projects
Availability. Although Wikimedia Foundation currently operates six data centers, MediaWiki is only running on one (in Ashburn, Virginia). If you are an editor in Jakarta, Indonesia, content has to travel over 15,000 kilometers to get from our servers to you (or vice versa). To run MediaWiki concurrently from multiple places across the globe, our code needs to be more resilient to failure modes that can occur when different subsystems are geographically remote from one another.

Performance testing infrastructure. WebPageTest provides a stable reference for a set of browsers, devices, and connection types from different points in the world. It collects very detailed telemetry that we use to find regressions and pinpoint where problems are coming from. This is addition to the more basic Navigation Timing metrics we gather from real users in production.

Media stack. We're currently working on overhauling our thumbnail infrastructure to achieve multiple goals. Improving future-proof maintainability by taking thumbnail code out of MediaWiki-Core and using a service instead to perform thumbnail operations. Saving on expensive storage by no longer storing multiple copies of all thumbnails on disk forever. Enabling far-future expires for images, to greatly improve their client cacheability. And finally switching to the best performing underlying software to generate thumbnails faster.

ResourceLoader. ResourceLoader is the MediaWiki subsystem that is responsible for loading JavaScript and CSS. Whereas much of MediaWiki's code executes only sparingly (in reaction to editors modifying content) ResourceLoader code runs over half a billion times a day on hundreds of millions of devices. Its contribution to how users experience our sites is very large. Our current focus is on improving ResourceLoader's cache efficiency by packaging and delivering JavaScript and CSS code in a way that allows it to be reused across page views without needing to be repeatedly downloaded.

Dashboards
A big part of our work is devoted to collecting and analyzing site performance data to ensure that we have a holistic and accurate understanding of what users experience when they access Wikimedia sites. You can discover our dashboards by visiting the Wikimedia performance portal. A selection of our dashboards is also provided here.
 * Navigation Timing
 * Job Queue Health
 * Media
 * ResourceLoader
 * WebPageTest
 * Save Timing
 * Asset Check
 * Edit Stash
 * MySQL aggregate

Display
Tracking performance requires different types of visualizations. Below are the tools we use for our dashboards and more.
 * Grafana
 * Coal-web
 * XHGui
 * PerformanceInspector
 * Flame graphs
 * Logstash Specifically the DBPerformance, DBReplication, mysql, memcached channels
 * Perflogbot An IRC bot on tracking ResourceLoader behavior
 * Dbtree Detailed MySQL data mostly obsoleted by Grafana MySQL dashboards
 * Xenon cli tools
 * Memkeys
 * WebPageTest

Processing/storage

 * Statsv
 * Coal
 * EventLogging
 * Statsd
 * Graphite
 * Xenon

Data sources

 * XHProf
 * WebPageTest
 * NavigationTiming
 * Asset check
 * MediaViewer
 * ResourceLoader
 * Varnish
 * Mediawiki
 * MariaDB

Milestones

 * Migration from Zend PHP to HHVM. This introduced a massive performance increase on backend response time.
 * Helped with the HTTPS+HTTP/2 migration.
 * Asynchronous ResourceLoader top queue.
 * DeferredUpdates. Greatly contributed to bringing edit save time median below 1 second.
 * WebPageTest. Now used by several teams to do synthetic performance testing.
 * Xenon/Flame graphs. Surfaces performance of all our PHP backend.
 * NavigationTiming improvements. We are now able to track real user performance in a more fine-frained fashion.
 * Introduction of many Grafana dashboards to track performance (see list above).
 * Statsv. Greatly simplifies sending data to statsd for frontend metric tracking.
 * Helped improve the new portal page performance
 * Helped on the images lazy loading project, which focused on improving the performance of the mobile site.

Links

 * Phabricator workboard
 * performance.wikimedia.org
 * IRC:
 * IRC: