Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Keeping Wikipedia fast [WeLoveSpeed]
Search
Peter Hedenskog
September 20, 2019
Technology
550
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Keeping Wikipedia fast [WeLoveSpeed]
Peter Hedenskog
September 20, 2019
More Decks by Peter Hedenskog
See All by Peter Hedenskog
Measuring Web Performance for Wikipedia using synthetic testing tools
soulislove
0
520
Measuring Web Performance Using Selenium
soulislove
2
990
Monitoring Web Performance using Open Source tools (Stockholm)
soulislove
2
270
Monitoring web performance using Open Source tools (San Francisco & Silicon Valley Web Performance Group)
soulislove
1
390
Monitoring web performance using Open Source tools (South Bay JavaScript Meetup)
soulislove
0
280
Optimise your home page (fast as lightning)
soulislove
1
81
Integrating performance tools into continuous delivery
soulislove
0
320
How to make your boss speed-curious and other webperf tricks - coldfront2014
soulislove
0
210
Sitespeed.io Lightning demo @ Velocity Santa Clara 2014
soulislove
0
150
Other Decks in Technology
See All in Technology
AI駆動開発で仕様はどこまで書くべきか? ― 人とAIの責務境界から考える開発プロセスの実践
takahiromatsui
1
270
あなたの知らないAmazon VPC Route Server/Amazon VPC Route Server you don't know about
masakiokuda
1
200
AIに書かせて、プラットフォームで縛る ― EKSプラットフォームで実践した責任境界と権限設計
elmodev09
1
1.1k
AI臭い文章とは何なのか
nasuvitz
37
76k
20260930_Gemma4_Hands-on
tsho
0
200
[Kiro Meetup #7] Kiro Crew Dive Deep
konippi
0
440
1人アドミンな私はAWSアカウント申請をSlackで完結したい!
ysuzuki
0
110
プラットフォームを「作る」、 チームに「入り込む」
sansantech
PRO
0
410
Claude Designがめちゃくちゃ便利なので使ってほしい
diggymo
0
170
Codex概要
ymiya55
0
140
【Findyテック文化祭ワークショップ】新卒エンジニア&採用担当と作る、 なりたい姿と今やるべき一歩
dip_tech
PRO
0
150
「大丈夫そう?」をObservabilityで確かめる
mrmtsu
0
240
Featured
See All Featured
The Impact of AI in SEO - AI Overviews June 2024 Edition
aleyda
6
1.2k
[Rails World 2026] Durable orchestration on Rails: from continuation to workflow
palkan
1
400
Unsuck your backbone
ammeep
672
58k
技術選定の審美眼(2025年版) / Understanding the Spiral of Technologies 2025 edition
twada
PRO
120
120k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
49
3.6k
Site-Speed That Sticks
csswizardry
13
1.5k
Utilizing Notion as your number one productivity tool
mfonobong
4
610
Context Engineering - Making Every Token Count
addyosmani
9
1.2k
Building Experiences: Design Systems, User Experience, and Full Site Editing
marktimemedia
1
610
Discover your Explorer Soul
emna__ayadi
2
1.3k
Side Projects
sachag
456
43k
Efficient Content Optimization with Google Search Console & Apps Script
katarinadahlin
PRO
1
890
Transcript
Keeping Wikipedia fast Peter Hedenskog - @soulislove
Keeping Wikipedia fast Peter Hedenskog - @soulislove
@soulislove
@soulislove Sweden France
@soulislove
@soulislove
What to do? @soulislove
@soulislove
@soulislove
@soulislove NO!!!!!
@soulislove Jean Bernadotte?
@soulislove
@soulislove Sweden France
@soulislove
@soulislove
@soulislove
Lets talk about performance @soulislove
@soulislove Today Our setup RUM & Synthetic Learnings I’ve got
the last four years Case study one regression
@soulislove https://news.ycombinator.com/item?id=20903868
@soulislove https://phabricator.wikimedia.org
@soulislove https://grafana.wikimedia.org
Why is performance important? @soulislove
We want to bring free knowledge to the world independently
of where you live and your economic status. @soulislove
@soulislove
Engineers/dev cares too! @soulislove
Why is performance hard (for us)? @soulislove
Keeping Wikipedia fast @soulislove https://news.ycombinator.com/item?id=20903868 Keeping Wikipedia fast is easy
right?
@soulislove
The Wikipedia Performance Team Challenge All Wikis are different (JS/CSS)
All pages are different (JS/CSS) All users are different (JS/CSS) @soulislove
Our history of performance testing @soulislove
PHP -> RUM-> Synthetic @soulislove
RUM @soulislove
@soulislove Metrics from real users Sampled (1/100) Buckets: platform, browser,
location https://github.com/wikimedia/mediawiki-extensions-NavigationTiming https://grafana.wikimedia.org/d/000000143/navigation-timing?refresh=5m&orgId=1
@soulislove
@soulislove
@soulislove
How we use RUM @soulislove Metrics from “all” users/scenarios Median,
75, 95, 99 - percentiles Alert on regressions First Paint / LoadEventEnd BFF with synthetic
Synthetic testing @soulislove
@soulislove
@soulislove Browsertime + WebPageReplay
That flat line @soulislove
Deviation @soulislove
How we use synthetic @soulislove Fixing the chaos (or creating
more?) Wayback machine Three URLs per alert First Visual Change BFF with RUM
Learnings: Synthetics @soulislove
Validate metrics! @soulislove
@soulislove
https://phabricator.wikimedia.org/T187981 @soulislove
@soulislove
page1 != page2 @soulislove
@soulislove Deviation
@soulislove User journey: second view
@soulislove User journey: second view
Server matters! @soulislove
1. AWS vs GCS vs other cloud providers 2. Servers
change over time (what runs on the same physical server?) 3. C4.xlarge != C4.xlarge @soulislove
@soulislove https://phabricator.wikimedia.org/T192138 https://phabricator.wikimedia.org/T192138 https://phabricator.wikimedia.org/T192138 https://youtu.be/pYbgcDfM2Ts?t=1575
Testing multiple steps are hard @soulislove
How long time do your user stay on each page?
How long do browsers keep HTTP connections open? @soulislove
Browser versions matter @soulislove
None
Know when browsers are updated!!! @soulislove
Learnings: RUM @soulislove
RUM can be good for finding regressions @soulislove
None
User Timing API != what shows on screen @soulislove
@soulislove
New element timings are better! @soulislove
@soulislove
Browser versions are important @soulislove
@soulislove
@soulislove
The hidden tabs incident @soulislove
@soulislove The idea: async all the things … use setTimeout
to run things later.
@soulislove https://phabricator.wikimedia.org/T146510 setTimeout
@soulislove https://phabricator.wikimedia.org/T146510
@soulislove 10% of the traffics opens in another tab!
What are we missing? @soulislove
@soulislove
@soulislove RUM Higher sample rate Buckets per page type Which
metrics are important?
@soulislove Synthetic Real mobile phones (T197847) Easier for devs to
add tests (T225416)
Case study: 3/9-2019 incident @soulislove https://phabricator.wikimedia.org/T231929
@soulislove Firefox
@soulislove Firefox
@soulislove Chrome
@soulislove Firefox
@soulislove WebPageTest
@soulislove
@soulislove TTFB? No: because visible with WebPageReplay
@soulislove ttfb?
@soulislove ttfb?
@soulislove ttfb?
@soulislove Screenshots/video Diff the HAR using https://compare.sitespeed.io or size per
content type in Graphite
@soulislove ttfb?
@soulislove We got 311 span class=“cs1-visible-error”!!! Citation errors: not shown
to readers https://en.wikipedia.org/wiki/Help:CS1_errors
@soulislove Credits Pippi and father - SVT Quick et Flupke
- Hergé The king shouting - Expressen The scream - Edward Munch Napoleon - Horace Vernet Engineers India Space Shuttle - Expressen Various pictures of Carl Gustaf - Swedish tax payers through the apanage
@soulislove Questions?? @soulislove
[email protected]