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

New Summary Metrics and Graph Updates – Another Great User Request

By: RedLine13

New Summary Metrics and Graph Updates

In a recent update we have added a few new calculated metrics to the summary section of load test results. These include a simple average of requests per second, errors per second, and data set per unit time. This request came from one of our users. We hope you will find it useful that we have calculated these data points in advance, as they are commonly used in final reports. Here is a preview of how you can expect to have this information presented:

New calculated metrics found in the summary section of test results
New calculated metrics will display in the summary section of both new tests as well as previously run tests.

In addition, this update also includes a minor bug fix to certain graphs on the test results page. Graph titles for requests, errors, and data per unit time now update dynamically to accurately reflect the reporting interval based on test duration (e.g., the interval may be per second, per minute, per 5 minutes, etc.). Also we have replaced the “Toggle Average” button with “Toggle Sum”, which provides a more intuitive and useful summation of all requests. Here is a example of an updated graph running a basic JMeter test:

Sample graph with updates depicting an JMeter load test example
Changes to requests, errors, and data per unit time will be available for both newly run tests and historical test data.

Requests per Second (rps) is one of the most important metrics that we care about during Load/Perf Test. It represents the process ability of server under the load testing. It’s important to see the amount of data going to and coming from the tested system. The higher the rps metric value, the better the performance of system. Having this value now auto calculated and displayed in the RedLine13 report, takes away the burden of manual calculation and verification.

S.Sindhu Kumar, Senior Software Quality Assurance Manager (IT), MyEG

It is our hope that incremental improvements like this will continue to increase the value of load testing services RedLine13 provides. If you don’t already have an account, sign up with our full-featured trial plan today!

2021-07-21
Previous Post: Conversation with RedLine13 Partner ThinkLogic
Next Post: StackShare Votes for RedLine13 – JMeter Users Love It

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

  • 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
  • AWS Multiple Account Setup for Load Testing – Securing your Application Environment
  • Case Study: Performance Test video streaming services with RedLine13
  • Free Load Test Trial
  • SAML SSO
  • E-Learning Companies and Load Testing
  • AWS Costs for Large JMeter Load Tests Run by Real Customers
  • Why BlazeMeter Customers Chose RedLine13

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

Designed using Responsive Brix. Powered by WordPress.