Though definitions may vary semantically depending on the unique characteristics of your application, there are many customers who choose RedLine13 for running their high volume JMeter load testing. In this article we will evaluate one customer’s experience on our platform, and also discuss why RedLine13 is ideally suited for your high volume JMeter testing needs.
One Customer’s Experience with RedLine13
A RedLine13 SaaS customer talked about using RedLine13 to run high volume load tests of 100 million requests per hour with JMeter and RedLine13 at the recent RedLine13 Customer Advisory Board meeting.
They first became a RedLine13 customer a little over a year ago and have ramped up quickly, running over 700 tests on RedLine13 in that time.
Their next step is to get the high volume tests into automation. They are doing this by leveraging the RedLine13 API, PowerShell scripts, Azure Pipelines, etc. They’ve also built a C# wrapper class for the RedLine13 API so that it can be called from code within Microsoft products.
Though they continue to use the web interface to manually run certain tests and collect those results, they prefer to use the API for high volume load tests where they “scale it up to the breaking point”. Of course scaling load-generating instances to high volumes is possible with manual test execution, the API leverages the power of automation.
“I really appreciate the API“.
– SaaS customer using RedLine13
They also talked about the future of load testing and how they see RedLine13 expanding the use of the API to help them. Here is the video of their talk.
High Volume JMeter Tests on RedLine13
With RedLine13, we have customers who routinely run JMeter tests at this volume and even much higher. It is an elementary task to write a JMeter test plan which generates a relatively high volume of requests. However, there are practical limitations to how many requests can be expected per a single load-generating instance. These constraints include networking performance, CPU load, memory, etc. The cloud based load testing architecture of RedLine13 effectively removes these constraints by leveraging parallel execution and multiplicity. In other words, once you have a JMeter test, you can simply “dial up” the load to any desired level in just a few short clicks.
One of the benefits of our platform is total abstraction of all load-generating server lifecycle and execution tasks. Upon clicking the “Start Test” button, there is little to do besides wait for the results to come in. RedLine13 also takes this a step further by automating the data collection from multiple parallel instances of your test and integrating this into combined tables and visualizations. This can be a huge timesaver for massively parallel JMeter test runs.
You can read about other RedLine13 customers who spoke at the RedLine13 Customer Advisory Board about why they chose RedLine13 and how they are using it.
You can try your own test, whether it is one request or a high volume test, on RedLine13 for free. We offer a full-featured trial which will enable you to evaluate the many features of our platform risk-free.