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

#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

  • Cost-Effective Cloud Load Testing
  • Guest Post: Load Testing with Locust and JMeter on RedLine13
  • Executing Gatling Tests with The SBT + Java RedLine13 Plugin
  • Selenium Load Testing: When and How
  • RedLine13 Basic vs Premium Subscription

Related

  • How to Run a Multi-Region Test – Available in Paid and Free Plans
  • Cost-Effective Cloud Load Testing
  • Guest Post: Load Testing with Locust and JMeter on RedLine13
  • Selenium Load Testing: When and How
  • Selecting Custom OpenJDK version for JMeter
  • Executing Gatling Tests with The SBT + Java RedLine13 Plugin
  • JMeter Alternatives: k6 and Gatling
  • RedLine13 Basic vs Premium Subscription
  • Speak the Lingo using Load Testing Terms
  • API Load Testing with cURL and RedLine13

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

Designed using Responsive Brix. Powered by WordPress.