This document compares Jmeter and Blazemeter for distributed performance testing. It discusses why distributed testing is needed to simulate large-scale loads and different geographical regions. It describes how distributed testing can be done locally by configuring Jmeter across multiple machines or by using cloud services like Blazemeter that provide scalable cloud agents. The combination of local and cloud agents is recommended to get the most realistic test results. Advantages of distributed testing include leveraging more resources to run large tests, while disadvantages include additional setup and maintenance costs.

3. Distributed Performance testing
Jmeter vs Blazemeter
Igor Cernopolc

4. What we are talking about?
www.amazon.com
 www.ebay.com

www.nytimes.com
 www.euronews.com

www.fifa.com
 www.facebook.com


5. Numbers first

6. Why do they work when we need them?
Pure luck?

7. Why do they work when we need them?
Designed
Developed

8. Why do they work when we need them?
Designed
Developed

9. Why distributed?

Insufficient power for larger scale projects

Geographical regions simulation

Realistic results (end to end)

10. 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

11. Solutions

Distributed on local infrastructure

Distributed on cloud

Dedicated cloud solutions

Combination between local and cloud

12. Distributed on local infrastructure
and
Firewalls on the systems are turned off
 Clients are on the same subnet
 Same version of JMeter on all the systems


13. 1. go to jmeter/bin
2. execute jmeter-server.bat
1.
2.
3.
go to jmeter/bin
open jmeter.properties
edit “remote_hosts=“
Multiplies
the script
on all
Slaves

14. Distributed on cloud

15. Dedicated cloud solutions

16. Combination between local and cloud
Best possible test results:
- cloud agents provide a realistic simulation of
end-users
- agents on the intranet can identify networkrelated issues and bottlenecks

17. Advantages

“Team work”

Distributed resources

Large-scale tests are possible

Tests are more realistic and accurate

18. 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


19. Disadvantages
Same configuration and resources should be
kept for comparability
 High costs of implementation and
maintenance

Cloud con’s

Application under test must be Internet facing
so that cloud agents can interact with it.

20. Conclusion
Do your magic before going live,
don't be a “Rio” example

21. Thank you
Igor Cernopolc
igor.cernopolc@gmail.com
November 2013