Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Ludicrous speed
Search
Sergey Vysotskiy
December 09, 2014
Technology
0
40
Ludicrous speed
Fantastic stories about performance requirements
Sergey Vysotskiy
December 09, 2014
Tweet
Share
More Decks by Sergey Vysotskiy
See All by Sergey Vysotskiy
Embracing the Imposter
ggame
0
49
Pressing Play at Spotify
ggame
0
69
Testing for capacity
ggame
2
230
Software Industry 101 (2013 season): Красочный мир тестирования
ggame
0
120
Latency
ggame
1
170
Швейцарский нож для Android
ggame
0
270
Анатомия ошибки
ggame
0
300
Other Decks in Technology
See All in Technology
コンパウンド組織のCRE #cre_meetup
layerx
PRO
1
250
Behind Postgres 18: The People, the Code, & the Invisible Work | Claire Giordano | PGConfEU 2025
clairegiordano
0
110
ソフトウェアエンジニアの生成AI活用と、これから
lycorptech_jp
PRO
0
860
SQLAlchemy の select(User).where(User.id =="123") を理解してみる/sqlalchemy deep dive
3l4l5
3
320
Zephyr(RTOS)にEdge AIを組み込んでみた話
iotengineer22
1
320
名刺メーカーDevグループ 紹介資料
sansan33
PRO
0
940
Databricks AI/BI Genie の「値ディクショナリー」をAmazonの奥地(S3)まで見に行く
kameitomohiro
1
400
20251027_マルチエージェントとは
almondo_event
0
120
ViteとTypeScriptのProject Referencesで 大規模モノレポのUIカタログのリリースサイクルを高速化する
shuta13
3
180
QA業務を変える(!?)AIを併用した不具合分析の実践
ma2ri
0
130
アウトプットから始めるOSSコントリビューション 〜eslint-plugin-vueの場合〜 #vuefes
bengo4com
3
1.7k
Observability — Extending Into Incident Response
nari_ex
1
120
Featured
See All Featured
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
130k
Bash Introduction
62gerente
615
210k
Embracing the Ebb and Flow
colly
88
4.9k
The Invisible Side of Design
smashingmag
302
51k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
230
22k
How to Ace a Technical Interview
jacobian
280
24k
Building a Scalable Design System with Sketch
lauravandoore
463
33k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
140
34k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.5k
Automating Front-end Workflow
addyosmani
1371
200k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
10
880
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
34
2.3k
Transcript
fantastic stories about performance requirements Ludicrous Speed
None
None
None
None
None
PANIC!
Modern human experimentations
None
None
Big business impact Big response delay
No silver bullets today
Perception of time What happens on internets? What is “OK”
response time? What is “OK” load? Summary PLAN
Perception of time What happens on internets? What is “OK”
response time? What is “OK” load? Summary PLAN
Perception of time What happens on internets? What is “OK”
response time? What is “OK” load? Summary PLAN
Perception of time What happens on internets? What is “OK”
response time? What is “OK” load? Summary PLAN
Perception of time What happens on internets? What is “OK”
response time? What is “OK” load? Summary PLAN
Perception Of Time
100-200 ms 500-1000 ms 2-5 seconds 7-10 seconds instantaneous reaction
uninterrupted reaction some reaction oof…
100-200 ms 500-1000 ms 2-5 seconds 7-10 seconds instantaneous reaction
uninterrupted reaction some reaction oof…
100-200 ms 500-1000 ms 2-5 seconds 7-10 seconds instantaneous reaction
uninterrupted reaction some reaction oof…
100-200 ms 500-1000 ms 2-5 seconds 7-10 seconds instantaneous reaction
uninterrupted reaction some reaction oof…
100-200 ms 500-1000 ms 2-5 seconds 7-10 seconds instantaneous reaction
uninterrupted reaction some reaction oof… *20 years old data
Modern data?
3… may be 5 seconds max
3… may be 5 seconds max Even faster in future
Weber–Fechner law 1 2
Weber–Fechner law 1 2
Weber–Fechner law 1 2
Weber–Fechner law 1 2
Weber–Fechner law 1 2 just noticeable difference (jnd)
Weber–Fechner law just noticeable difference (jnd) For time lengths of
up to 30s - jnd is somewhere between 7% and 18%
Weber–Fechner law Faster Slower
Weber–Fechner law 20s Faster Slower
Weber–Fechner law 20s 24s 16s -20% +20% Faster Slower
“Slightly” faster
Perception of average between t1 and t2 is: sqrt(t1*t2)
Example
Benchmark against 30s 60s less than 36s less than 42s
less than 24s slow same slightly slower faster
Benchmark against 30s 60s less than 36s less than 42s
less than 24s slow same slightly slower faster
Benchmark against 30s 60s less than 36s less than 42s
less than 24s slow same slightly slower faster
Benchmark against 30s 60s less than 36s less than 42s
less than 24s slow same slightly slower definitely faster
Is it worth to optimise? Target performance Unnoticeable degradation
Is it worth to optimise? Target performance Unnoticeable degradation
Is it worth to optimise? Target performance Unnoticeable degradation
Why so serious?
Why so serious?
What Happens on Internets?
None
None
Response time: DNS request Establish TCP connection Generate request to
server Send request to server Server generates response Server sends response Page rendering on browser
Response time: DNS request Establish TCP connection Generate request to
server Send request to server Server generates response Server sends response Page rendering on browser
Response time: DNS request Establish TCP connection Generate request to
server Send request to server Server generates response Server sends response Page rendering on browser
Response time: DNS request Establish TCP connection Generate request to
server Send request to server Server generates response Server sends response Page rendering on browser
Response time: DNS request Establish TCP connection Generate request to
server Send request to server Server generates response Server sends response Page rendering on browser
Response time: DNS request Establish TCP connection Generate request to
server Send request to server Server generates response Server sends response Page rendering on browser
Response time: DNS request Establish TCP connection Generate request to
server Send request to server Server generates response Server sends response Page rendering in a browser
Response time: DNS request Establish TCP connection Generate request to
server Send request to server Server generates response Server sends response Page rendering in a browser
Fun facts! Min time to pass 1/2 of globe: 67ms
Later ;) Server generates response
Let’s talk a bit about that Page rendering in a
browser
In a complex projects 60% of time could be easily
spent on rendering
There’s space to optimise
There’s space to optimise
There’s space to optimise
Time budget: Load and render critical parts first
What Is “OK” Response?
It depends
In general case response longer than 300ms means nobody cares
In general case response longer than 300ms means nobody cares
Usually it’s more than 1 second on a client
It should be fast
It should be fast Bad requirement
It should be faster than 300ms
It should be faster than 300ms Bad requirement
Long tail
95% < 300ms 99% < 500ms
95% < 300ms 99% < 500ms
95% < 300ms 99% < 500ms OK requirement
95% < 300ms 99% < 500ms OK requirement But still
depends
Remember about 20% difference!
Remember to measure competitors!
Oof… Done with time!
Oof… Done with time! There are 1 more to go
What Is “OK” Load?
What measurement units to use?
What is “average user”?
“Average human” have less than 1 arm
Requests Per Second (RPS) is what server understands
How much RPS we should be able to handle?
EXTREMELY HARD QUESTION
Pulse of the Web
Spotify Average Monday in Stockholm
Spotify Specific Monday in Stockholm
None
None
None
None
Spotify Average Monday in Eastern US
Financial Times weekly traffic changes
Financial Times weekly traffic changes Extremely different for different clients
Financial Times weekly traffic changes Extreme daily features
Thanksgiving in US Events could make a big difference
Bombing in Moscow subway 29 march 2010
Bombing in Moscow subway 29 march 2010 First explosion 7:57
Load growth 8:10
Think like a user Look for daily/weakly/yearly cycles
Think like a user Look for daily/weakly/yearly cycles
Event based service? Prepare for extremely huge spikes
Do closed beta And watch for load profile
It’s growing
Very Short Summary
Find out what is OK response time for you Remember
about long tail Find out possible max load Test your assumptions
Find out what is OK response time for you Remember
about long tail Find out possible max load Test your assumptions
Find out what is OK response time for you Remember
about long tail Find out possible max load Test your assumptions
Find out what is OK response time for you Remember
about long tail Find out possible max load Test your assumptions
APPLAUSE
QUESTIONS?
Magic Numbers Some
4 datacenters More than 5K servers ~50 millions of unique
users More than 100 people working on backend infrastructure and operations
DATACENTERS: Ashburn San Jose Stockholm London
QUESTIONS?
Sergey Vysotskiy
[email protected]