Operations

  1. How we made editing Wikipedia twice as fast

    "MediaWiki flame graph screenshot 2014-12-15 22"

    The creator of the wiki, Ward Cunningham, wanted to make it fast and easy to edit web pages. Cunningham named his software after a Hawaiian word for “quick.” That’s why the Wikimedia Foundation is happy to report that editing Wikipedia is now twice as quick. Over the last six months we deployed a new technology that speeds up MediaWiki, Wikipedia’s underlying PHP-based code. HipHop Virtual... Read more

  2. Protecting users against POODLE by removing SSL 3.0 support

    "Pudel-drawing" by Gustav Mützel (Brehms Tierleben), public domain

    To protect our users against the recently disclosed POODLE security vulnerability, we are removing support for SSL 3.0 on all Wikimedia sites as of 15:00 UTC (8:00 am PDT) today.
    SSL 3.0 is an outdated implementation of the HTTPS web encryption protocol. […]... Read more

  3. Making Wikimedia Sites faster

    "Improvement in Page Load Times on Wikipedia after the ULSFO datacenter deployment (mapped with carto db)" by NRuiz (WMF), under CC-BY-SA-3.0

    Running the fifth largest website in the world brings its own set of challenges. One particularly important issue is the time it takes to render a page in your browser. Nobody likes slow websites, and we know from research that even small delays lead visitors to leave the site. An ongoing concern from both the Operations and Platform teams is to improve the reader experience by making Wikipedia an... Read more

  4. How RIPE Atlas Helped Wikipedia Users

    "Latency map world" by Drdee, under CC-BY-SA-2.5

    This post by Emile Aben is cross-posted from RIPE Labs, a blog maintained by the Réseaux IP Européens Network Coordination Centre (RIPE NCC). In addition to being the Regional Internet Registry for Europe, the Middle East and parts of Central Asia, the RIPE NCC also operates RIPE Atlas, a global measurement network that collects data on Internet connectivity and reachability to assess the state... Read more

  5. Wikimedia Foundation selects CyrusOne in Dallas as new data center

    In October 2013, we launched a public request for proposals regarding a new data center location in the continental US for co-locating Wikimedia infrastructure. We’ve now concluded this process and selected the CyrusOne facility in Dallas/Carrollton. Wikimedia’s primary data center is in Ashburn, Virginia, and we’ve been preparing to end our remaining hosting presence in Tampa, Florida (whic... Read more

  6. Migrating Wikimedia Labs to a new Data Center

    As part of ongoing efforts to reduce our reliance on our Tampa, Florida data center, we have just moved Wikimedia Labs to EQIAD, the new data center in Ashburn, Virginia. This migration was a multi-month project and involved hard work on the part of dozens of technical volunteers. In addition to reducing our reliance on the Tampa data center, this move should provide quite a few benefits to the us... Read more

  7. Request for proposals: New datacenter in the continental US

    The Wikimedia Foundation’s Technical Operations team is seeking proposals on the provisioning of a new datacenter facility. After working through the specifics internally, we now have a public RFP posted and ready for proposals. We invite any organization meeting the requirements outlined to submit a proposal for review. Most of the relevant details are in the document itself, but feel free ... Read more

  8. HTTPS by default beta program

    Now that we’ve enabled HTTPS by default for logged-in users, our next major objective is to enable HTTPS by default for anonymous users. We have a number of steps to take to arrive at this goal, including a couple important initial steps, such as conducting proper testing for load and shaking out bugs on smaller scale deployments before mass deployment. For both load testing and shaking out ... Read more

  9. HTTPS enabled by default for logged-in users on Wikimedia sites

    Today, August 28, the Wikimedia Foundation is making a change to the software that powers the Wikimedia projects: By default, all logged-in users will now be using HTTPS to access Wikimedia sites. What this does is encrypt the connection between the Wikimedia servers and the user’s browser so that the information sent between the two is not readable by anyone else. This is in response to the... Read more

  10. The future of HTTPS on Wikimedia projects

    The Wikimedia Foundation believes strongly in protecting the privacy of its readers and editors. Recent leaks of the NSA’s XKeyscore program have prompted our community members to push for the use of HTTPS by default for the Wikimedia projects. Thankfully, this is already a project that was being considered for this year’s official roadmap and it has been on our unofficial roadmap sinc... Read more