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

Running a URL Load Test

By: RedLine13

In this video we will demonstrate how to run a simple URL test to gauge performance of a website. If you’re new to load testing, this is the easiest test to run on RedLine13.

Getting Started

When running a URL test on RedLine13, begin by logging into your account, hit “Start Test”, and then click the “Simple Test” tab. Next, begin to enter the parameters of your load test. In this example we will have 100 virtual users access StackOverflow. We have a 3 second ramp-up-time, a minimum delay of 500 ms, and a maximum delay of 10,000 ms:

 

url-load-testing-redline13

Configure Servers and Run Test

Next, expand the “Advanced Cloud Options” tab. Here you control your load agents. You can select the type/size/number/location of the servers, edit security groups, and more. In this example we will be testing on two m3.medium servers in Germany, with 50 users per server:

url-load-testing-redline13_aco

If needed, we can expand the “Advanced Simple Test Options” to add and GET/POST parameters. Finally, name your test and hit “Start Test” to begin. The servers will spin up and your test will begin shorty.

url-load-testing-redline13_

Analyze Results

Once the test has completed we can then view our results. Here we are presented with an overview and breakdown of everything that happened during the test. You will find:

  • Response/request metrics
  • Percentile results (Pro)
  • Overview metrics (threads per second, average thread elapsed time, etc.)
  • Error metrics (error response time, errors per second, etc.)
  • Load agent metrics (load agent CPU usage, bytes received/transmitted, etc.)
  • Server output files (.tgz)
  • + more

In this example we found that out of the 1,100 requests made, 99% were completed in 11.69 seconds. Some 100 pages were tested and our load test costed us only $0.17 cents in total, making it an affordable solution to test URLs.

url-load-testing-redline13_metrics

2017-02-01
Previous Post: Running a Custom Python Load Test
Next Post: Shift Left Testing: What It Is & Why You Should Do It

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.