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

Starting Up Load Agents

By: Rich Friedman

AWS Spot Instance Startup

When you first start a test, there is an initial wait time for RedLine to provision the Spot Instances in your AWS account. Then we have to load the tests scripts and get things synced. This only happens the first time you are starting up those spot instances.  As long as you keep using them, you will not have the wait time. Of course if you run your tests and then let the spot instances die, then come back the next day, the process needs to repeat itself.

We provide a message when you start each test to remind you what is going on.

2013-08-11
Previous Post: CSV Data Download for Load Testing
Next Post: Load Testing Red Hat OpenShift

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

  • Case Study: iCIMS, The Talent Acquisition Software Experts
  • 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

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

Designed using Responsive Brix. Powered by WordPress.