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
Agile performance testing
Search
Andreas Bjärlestam
March 30, 2016
Programming
0
110
Agile performance testing
Agile performance testing with Amazon AWS, tmux and siege
Andreas Bjärlestam
March 30, 2016
Tweet
Share
More Decks by Andreas Bjärlestam
See All by Andreas Bjärlestam
Climate compensate with a pull request
bjarlestam
0
31
SPDY and HTTP2
bjarlestam
1
1.2k
SPDY or maybe HTTP2.0
bjarlestam
4
62
jquery mobile
bjarlestam
0
70
Devise - taking care of your users
bjarlestam
0
71
REST with JAX-RS
bjarlestam
1
89
REST
bjarlestam
2
170
Other Decks in Programming
See All in Programming
プロパティベーステストによるUIテスト: LLMによるプロパティ定義生成でエッジケースを捉える
tetta_pdnt
0
3.3k
Tool Catalog Agent for Bedrock AgentCore Gateway
licux
7
2.5k
AI Agents: How Do They Work and How to Build Them @ Shift 2025
slobodan
0
100
🔨 小さなビルドシステムを作る
momeemt
4
690
Ruby Parser progress report 2025
yui_knk
1
460
AWS発のAIエディタKiroを使ってみた
iriikeita
1
190
個人開発で徳島大学生60%以上の心を掴んだアプリ、そして手放した話
akidon0000
1
150
Laravel Boost 超入門
fire_arlo
3
220
知っているようで知らない"rails new"の世界 / The World of "rails new" You Think You Know but Don't
luccafort
PRO
1
190
FindyにおけるTakumi活用と脆弱性管理のこれから
rvirus0817
0
540
The Past, Present, and Future of Enterprise Java
ivargrimstad
0
410
実用的なGOCACHEPROG実装をするために / golang.tokyo #40
mazrean
1
290
Featured
See All Featured
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
36
2.5k
Site-Speed That Sticks
csswizardry
10
820
Done Done
chrislema
185
16k
Bash Introduction
62gerente
615
210k
Why Our Code Smells
bkeepers
PRO
339
57k
Building Applications with DynamoDB
mza
96
6.6k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
52
5.6k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
44
2.5k
Why You Should Never Use an ORM
jnunemaker
PRO
59
9.5k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
285
14k
Six Lessons from altMBA
skipperchong
28
4k
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
18
1.1k
Transcript
Understanding your system Andreas Bjärlestam! 2016-03-30! _____ .__.__ / _
\ ____ |__| | ____ / /_\ \ / ___\| | | _/ __ \ / | \/ /_/ > | |_\ ___/ \____|__ /\___ /|__|____/\___ > \//_____/ \/ _____ ______ ____________/ ____\___________ _____ _____ ____ ____ ____ \____ \_/ __ \_ __ \ __\/ _ \_ __ \/ \\__ \ / \_/ ___\/ __ \ | |_> > ___/| | \/| | ( <_> ) | \/ Y Y \/ __ \| | \ \__\ ___/ | __/ \___ >__| |__| \____/|__| |__|_| (____ /___| /\___ >___ > |__| \/ \/ \/ \/ \/ \/ __ __ .__ _/ |_ ____ _______/ |_|__| ____ ____ \ __\/ __ \ / ___/\ __\ |/ \ / ___\ | | \ ___/ \___ \ | | | | | \/ /_/ > |__| \___ >____ > |__| |__|___| /\___ / \/ \/ \//_____/
Do you know on top of your head: • How
many req/s your system can handle? • What response >me it has? • How it scales? • What the bo@lenecks are? • How stable it is over >me?
Many s>ll do big bang performance tes>ng
Stop seeing performance tests as verifica>on It should be an
integrated part of your development cycle Con>nuously analyze your system
You should do it all the >me!
I’m lazy, so performance tes>ng must be quick and simple
isola>on
Your test client should do nothing but loadtes>ng, no interference
Amazon AWS + tmux = win!
You can leave it on and come back to check
every now and then
Combine with monitoring: Newrelic Kibana Graphite
> sudo yum install siege
> siege -c10 -t30s -d1 -i -f urls.txt
siege • Quick and simple • Instant visual feedback •
Good summary of most important metrics • Good enough for most scenarios = You can work in quick itera>ons
Create a Traffic Model
Your best guess of how the system will be used
When replacing a system Get access logs from the old
system Analyze which parts of the system that generate the most load Plot them over >me to get a feeling for peaks and average load
If you replay access logs against your system with siege
you can gain a lot of insights and find problems like unhandled urls, unnecessary redirects etc
Build a urls.txt file Based on traffic model Fill a
file with urls that represent your expected traffic, one url per line Think about the propor>ons of different types of urls
Build a urls.txt file Expec>ng broad traffic -> many urls
Expec>ng narrow traffic -> not so many
Build a urls.txt file h@p://example.com h@p://example.com/user/s>na h@p://example.com/user/olof h@p://example.com/user/sven h@p://example.com/user/siv h@p://example.com/user/ellen
h@p://example.com/country/sweden h@p://example.com/country/norway
Build a urls.txt file curl cut jq grep etc are
your friends
Build a urls.txt file You can send POST as well
h@p://example.com/user/s>na POST age=23 h@p://example.com/user/s>na POST a=1&b=2 h@p://example.com/user/s>na POST <./s>na.txt
Finding the system limits
10 req/s OK 100 req/s OK 500 req/s Slooow 300
req/s OK
Scale up with more CPU or processors and try again
Does it scale linearly?
This is a good >me to think about the bo@lenecks
of your system I/O CPU Sync / Async
Adjust and try again
Keep an eye on system metrics Response >me CPU load
Memory usage Error rates etc
Stability tes>ng
Start a linux machine on AWS Set up a session
with tmux Start siege Leave it running
> siege -c10 -t24h -i -d1 -f urls.txt
Put your system under con>nuous load from your first commit
Keep an eye on system metrics every now and then
Good to know: siege counts error responses and will stop
if it encounters more than 1024 errors
TLDR Stop doing performance tests like its 1999 Put your
system under load from day 1 Run tests interac>vely, be crea>ve Gain understanding AWS + tmux + siege is awesome!
tmux cheat sheet > tmux new -s loadtest starts a
new session named loadtest ctrl-b + d exits session > tmux list-sessions lists all current sessions > tmux a@ach -t loadtest a@aches to the session named loadtest
If siege does not fit your use case You could
try - gatling - locust - wrk They are bigger (more complex) hammers