Skip to content
  • ZipCode Api
  • Blog
  • About RedLine13
RedLine13
RedLine13
Primary Navigation Menu
Menu
  • Start Testing
  • Demo
  • Pricing
  • JMeter
  • Partners
  • Docs
    • Documentation Home
    • AWS Set Up for load testing
    • AWS Approval for Large Tests
    • PHP, NodeJS, Python Load Tests
    • Scalability
    • Jenkins Plugin Setup
    • Premium Features
    • Knowledge Base

Apache JMeter Load Testing – Scaling in the Cloud

By: RedLine13

JMeter is an excellent open source load testing tool used by thousands of developers. If you want to scale your tests you have some options. You can do it yourself. Or you can scale out your JMeter test on the cloud with RedLine13.

JMeter Load Testing – Do It Yourself

Scaling JMeter beyond 500-1000 users increases complexity and setup time.

Additionally, JMeter reports are usually displayed at the end of the test and only exist locally. There’s no built-in way to share or collaborate.

If you want to do it yourself, here is what you’ll need to consider to run load tests with JMeter.

JMeter works across servers, since JMeter instances support RMI protocol. You’ll have a Master (your desktop) and some number of Agents, say 10. The Master will send commands to  the 10 agents. The issue is that your laptop can not easily connect to your AWS/Cloud environment

Then you’ll play around with network rules, maybe opening up every port which makes your environment insecure.
And when your test finishes you have to clean up all your security issues.

Here’s a very high level overview of what you’d need to do it yourself:

1.  Use the AWS console or API to start up X servers, however many you want.
2.  Install all the required packages on each of those servers.  (You could do this once, create an AMI, copy it to the regions you plan to use, then start servers based on that AMI).
3.  Set up a scheduler to start all the tests at the same time on each of those servers.
4.  You’ll probably want to have a quick way to stop all tests on all servers if it’s impacting your site too much.
5.  Collect the JMeter output files after the test.  This is assuming you don’t want to put in the effort to create real-time reports.
6.  Write tools to combine the JMeter files into a final report.
At this point, you may be asking yourself if this is the best way to do it. And if it takes you more than an hour a month, you could have paid for a monthly subscription to Redline13.

JMeter Load Testing – With RedLine13

Scaling out your JMeter test plan on the cloud in RedLine13 is easy. In this video and subsequent guide, we will walk you through running you first JMeter test on RedLine13.
2018-03-22
Previous Post: WebDriver Chrome and Firefox Headless Load Testing
Next Post: Improve Your WebSocket Application Performance

Recent Posts

  • JMeter XML Format Post Processor
  • Order of Elements in JMeter
  • The JMeter Synthesis Report
  • Using the JMeter Plugins Manager
  • JMeter Rotating JTL Listener

Related

  • JMeter XML Format Post Processor
  • Order of Elements in JMeter
  • The JMeter Synthesis Report
  • Using the JMeter Plugins Manager
  • JMeter Rotating JTL Listener
  • Using Test Fragments in JMeter Tests
  • Step-by-Step Guide to Testing with JMeter
  • Functional Testing vs Performance Testing
  • A Gentle Introduction to Load Testing
  • Using the JMeter Counter Element

© RedLine13, LLC | Privacy Policy | Contract
Contact Us: info@redline13.com

Designed using Responsive Brix. Powered by WordPress.