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

JMeter Cloud testing your DB

By: Rich Friedman

At times, we want to know the performance of our database queries under load.  These type of load tests would rarely be tested from locations outside your infrastructure.  Opening holes directly to a database in the open would be a poor security model.

Redline13 JMeter Load Testing allows you to easily deploy JMeter load plans inside your AWS domain and hammer away with your queries. 

In this load test, we started a MySQL instance creating a table called countries, which we sourced from this country data source.

Our Load Plan is to launch 5 servers each starting 200 users iterating 50 times and ramping over 5 minutes.   That would give us 50,000 queries over a few minutes. 

  1. We add a JDBC Configuration, selecting information for our Mysql/JDBC setup.
    • Screen Shot 2015-02-11 at 11.40.49 PM
  2. Add a JDBC Request to make our query
    • Screen Shot 2015-02-11 at 11.41.38 PM
  3. Building our Redline13 Load Plan 
    1. Drop in your JMX File
    2. Drop in your JAR file for the DB connection library
      • In our case, we are using MYSQL 
      • Screen Shot 2015-02-11 at 11.42.52 PM
    3. Select your instance Types and Configure Subnet ID if appropriate
      • Screen Shot 2015-02-11 at 11.44.02 PM
  4. Run your test! 
    1. Oops, we had plenty of success calls but we did find an issue.  Our database instance has limited total connections and we can see that in our error section. 
      • Screen Shot 2015-02-11 at 11.48.53 PM
    2. We changed our configuration and ran our test again.
  5. Sample Output
    • Screen Shot 2015-02-11 at 11.50.08 PM

The results and copy of the test are available on the results page. 

2015-02-12
Previous Post: JMeter Load Testing against Public APIs (Bing Use Case)
Next Post: JMeter Large Project Support

Recent Posts

  • Load Testing with AWS Spot vs On-Demand Instances – Spot Instances save you money
  • How many vCPUs needed for Load Testing?
  • Simple View of Security at RedLine13
  • Use Cases for the JMeter Dashboard Report
  • AWS Costs for Large JMeter Load Tests Run by Real Customers

Related

  • Free Load Test Trial
  • AWS Costs for Large JMeter Load Tests Run by Real Customers
  • JMeter Soak Testing and What it Costs
  • Partner Case Study: E-commerce Load Testing using JMeter and RedLine13
  • Customer Saves 90% vs. BlazeMeter with RedLine13
  • MSD Animal Health Intelligence Technology Labs talks about the ease of using Jmeter and RedLine13
  • Automatically stop a JMeter load test after too many errors
  • Accessing JMeter Properties set as Command Line Options
  • StackShare Votes for RedLine13 – JMeter Users Love It
  • Most Popular Load Test Types Over The Years – JMeter Keeps Growing

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

Designed using Responsive Brix. Powered by WordPress.