Distributed load testing (Local vs Cloud)

477 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
477
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Distributed load testing (Local vs Cloud)

  1. 1. Distributed Performance testing Jmeter vs Blazemeter Igor Cernopolc
  2. 2. What we are talking about? www.amazon.com  www.ebay.com  www.nytimes.com  www.euronews.com  www.fifa.com  www.facebook.com 
  3. 3. Numbers first
  4. 4. Why do they work when we need them? Pure luck?
  5. 5. Why do they work when we need them? Designed Developed
  6. 6. Why do they work when we need them? Designed Developed
  7. 7. Why distributed?  Insufficient power for larger scale projects  Geographical regions simulation  Realistic results (end to end)
  8. 8. 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
  9. 9. Solutions  Distributed on local infrastructure  Distributed on cloud  Dedicated cloud solutions  Combination between local and cloud
  10. 10. 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 
  11. 11. 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
  12. 12. Distributed on cloud
  13. 13. Dedicated cloud solutions
  14. 14. 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
  15. 15. Advantages  “Team work”  Distributed resources  Large-scale tests are possible  Tests are more realistic and accurate
  16. 16. 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 
  17. 17. 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.
  18. 18. Conclusion Do your magic before going live, don't be a “Rio” example
  19. 19. Thank you Igor Cernopolc igor.cernopolc@gmail.com November 2013

×