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

Why ACT Moved to RedLine13

By: Chris Baeckstrom

Heath Meyer of ACT spoke at LoadTestWorld about why ACT moved to RedLine13 and how they did it. Read below for the highlights of Heath’s talk or watch his 28 minute video on the LoadTestWorld YouTube channel.

Moved to RedLine13

Periodic Exploration

Heath explained how ACT regularly does periodic explorations of new technology and that is how they learned about RedLine13. ACT evaluated the new technology based on:

  • cost
  • ease of use
  • support
  • ability to leverage existing scripts

Savings

ACT did an analysis of RedLine13 versus their existing platform.

We saw there was going to be significant savings. We were hitting ceilings with our existing contract. And then we’d have additional costs above that. The RedLine13 approach was different. If we had slow times and weren’t testing, we didn’t have those costs that we had to pay the previous platform whether we were testing or not.

Heath Meyer, ACT

Ease of Use

ACT was able to stand up their POC within a few weeks.

We were able to ramp up pretty darn quick.

Heath Meyer, ACT

Support

ACT was happy with the ability to reach out directly and get feedback. They were also happy with the responsiveness and how RedLine13 pointed them in the right direction as they quickly came up to speed.

With the previous company we dealt with, we’d be looking for some information and we had to write up a support ticket and wait a day or two, and before you knew it, we were falling behind.

Heath Meyer, ACT

Leverage Existing Technology

ACT had a lot of JMeter scripts in their previous dashboard and their infrastructure was AWS so everything easily moved to RedLine13.

Pilot

ACT took their existing scripts and ran a parallel process with their existing platform and RedLine13. They then compared the results and the costs.

The Pilot results showed that we were able to leverage our existing scripts with minimal effort. Both the tool and the execution cost was dramatically reduced. We do an annual checkup and we continue to be far below what we paid before.

Heath Meyer, ACT

ACT found that their existing dashboard had more capabilities than RedLine13. But they found that they were either nice-to-haves or they could leverage the AWS tools they already had in place.

Transition to RedLine13

With ACT’s use of JMeter and AWS, they were able to transition easily as described above. Some of the key items: support, documentation and dashboard simplicity.

RedLine13 Trial Subscription

If you’re considering changing your load testing platform, you can test drive RedLine13 with our free trial. Sign up and start testing today.

2021-11-02
Previous Post: yCrash Answers Performance Testing Questions – A Complement to RedLine13
Next Post: RedLine13 Load Testing Alerts

Recent Posts

  • JMeter XML Format Post Processor
  • Order of Elements in JMeter
  • The JMeter Synthesis Report
  • Using the JMeter Plugins Manager
  • JMeter Rotating JTL Listener

Related

  • JMeter XML Format Post Processor
  • Order of Elements in JMeter
  • The JMeter Synthesis Report
  • Using the JMeter Plugins Manager
  • JMeter Rotating JTL Listener
  • Using Test Fragments in JMeter Tests
  • Step-by-Step Guide to Testing with JMeter
  • Functional Testing vs Performance Testing
  • A Gentle Introduction to Load Testing
  • Using the JMeter Counter Element

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

Designed using Responsive Brix. Powered by WordPress.