distributed load testing (local vs cloud)
TRANSCRIPT
Distributed Performance testing
Jmeter vs Blazemeter
Igor Cernopolc
What we are talking about?
www.amazon.com www.ebay.com
www.nytimes.com www.euronews.com
www.fifa.com www.facebook.com
Numbers first
Why do they work when we need them?
Pure luck?
Why do they work when we need them?
Designed Developed
Why do they work when we need them?
Designed Developed
Why distributed?
Insufficient power for larger scale projects
Geographical regions simulation
Realistic results (end to end)
How can we do that?
Classic way Computer - lots of them, wires, routers, people, scripts, more computers an so on
Modern way Cloud, dedicated tools, dedicated environments
Solutions
Distributed on local infrastructure
Distributed on cloud
Dedicated cloud solutions
Combination between local and cloud
Distributed on local infrastructure
Firewalls on the systems are turned off Clients are on the same subnet Same version of JMeter on all the systems
and
1. go to jmeter/bin 2. execute jmeter-server.bat
Multiplies the script
on all Slaves
1. go to jmeter/bin2. open jmeter.properties3. edit “remote_hosts=“
Distributed on cloud
Dedicated cloud solutions
Combination between local and cloud
Best possible test results:- cloud agents provide a realistic simulation of
end-users - agents on the intranet can identify network-
related issues and bottlenecks
Advantages
“Team work”
Distributed resources
Large-scale tests are possible
Tests are more realistic and accurate
Cloud pro’s
Better geographical areas coverage No setup or maintenance required Easy and fast deployment Scalability: If you need more agents, just
launch them Easy management Low cost: Only pay for the time the agents
are running No limits
Disadvantages
Same configuration and resources should be kept for comparability
High costs of implementation and maintenance
Application under test must be Internet facing so that cloud agents can interact with it.
Cloud con’s
Conclusion
Do your magic before going live,
don't be a “Rio” example
