Skip to content
  • ZipCode Api
  • Blog
  • About RedLine13
RedLine13
Primary Navigation Menu
Menu
  • Start Testing
  • Demo
  • Pricing
  • Docs
    • Knowledge Base
    • AWS IAM Setup Instructions
    • Running a RedLine13 Load Test with Advanced Options
    • Scalability
    • Writing Open Load Tests in Your Language
    • Jenkins Plugin Setup
    • AWS Approval for Large Tests
    • Pro Features
  • JMeter
  • Partners

#7 How it should work

By: Rich Friedman

From the Open Source Load Testing presentation http://www.slideshare.net/richardfriedman/open-source-load-testing

In the previous (#6 How it Used To Work), I told a story of how we put our desktops, yes desktops, to work. However, in today’s world, there are many more options.   You can rent agents from other commercial load testing clouds or you could use your own cloud to generate the test load.  Each team can now have their own environment and the dependency friction gets removed.

Stephen Sigwart (CTO at RunSignUp.com and founder at RedLine13) needed to meet the requirements of scaling to 50,000 registrations in ten minutes.  Knowing that this would be a very iterative process and the commercial agents would be above his budget, he built the original RedLine13 to support ‘How it should work’.

  • You.  No minions… just you launching a multi-thousand user load test.
  • Test Plan. The process of creating a load test plan has improved over the years (still can be better), but that should be all you need to start the process.
  • Cloud.  Where your agents will be created and scale to your requirements
  • Servers. Your staging or production environment, and if you are following strong dev-ops practices, the task of having a mirror environment could be easier than ever.

The goal of load testing is to find performance bottlenecks, the act of load testing should get out of the way.

OSLT_HowItShouldWork

2015-09-03
Previous Post: #6 How it used to work
Next Post: Knowledge Base and Trail Maps

Recent Posts

  • Use Cases for the JMeter Dashboard Report
  • AWS Costs for Large JMeter Load Tests Run by Real Customers
  • AWS Multiple Account Setup for Load Testing – Securing your Application Environment
  • Merge Results for Data Analysis
  • Debug your JMeter Test with Output Files

Related

  • Use Cases for the JMeter Dashboard Report
  • AWS Costs for Large JMeter Load Tests Run by Real Customers
  • AWS Multiple Account Setup for Load Testing – Securing your Application Environment
  • Merge Results for Data Analysis
  • Compare Load Tests Results using CSV Data
  • Debug your JMeter Test with Output Files
  • Integrating your AWS and RedLine13 accounts
  • Signing Up for AWS is Easy and Free
  • Enabling Public IPs on your RedLine13 Load Generators
  • JMeter Test Capacity Limits

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