{"id":8470,"date":"2021-11-24T15:01:24","date_gmt":"2021-11-24T20:01:24","guid":{"rendered":"https:\/\/www.redline13.com\/blog\/?p=8470"},"modified":"2022-05-23T13:05:12","modified_gmt":"2022-05-23T17:05:12","slug":"redline13-versus-diy","status":"publish","type":"post","link":"https:\/\/www.redline13.com\/blog\/2021\/11\/redline13-versus-diy\/","title":{"rendered":"Managed versus Do-it-Yourself JMeter Load Testing"},"content":{"rendered":"

<\/a> \"RedLine13<\/p>\n

JMeter is one of the most popular load testing frameworks. However, to use JMeter at scale requires supporting infrastructure. In this post, we will be comparing and contrasting managed versus do-it-yourself (DIY) JMeter load testing.<\/p>\n

With the rise of cloud-based architectures, it has become increasingly the standard to test using cloud-based resources. This means writing scripts to provision servers, coordinate load generators, and handle data collection.\u00a0 Load testers using JMeter have two general options. They can opt to design and build the entire stack themselves as a \u201cDIY<\/em>\u201d approach. Alternatively testers can use ready-made solutions such as RedLine13 to abstract away everything except for the actual load test.<\/p>\n

<\/a>RedLine13 is Fully Managed<\/h3>\n

One advantage to using RedLine13 over a DIY approach is that it is fully managed. You can access your tests from anywhere and at any time through an easy to use web portal. Support exists for multiple test types \u201cout-of-the-box\u201d, including JMeter<\/a>, Gatling<\/a>, custom scripting<\/a>, and more<\/a>.<\/p>\n

JMeter itself is a command-line tool, and though there is a GUI mode it is not optimal to generate load in this way. This necessitates coordinating often multiple instances across multiple load generating servers, which requires significant infrastructure programming. With some time and effort invested this is entirely possible with the DIY approach, however RedLine13 makes it easy by providing all of this functionality. This can be a significant advantage for small teams who might want to focus on writing actual tests versus investing in a custom test infrastructure.<\/p>\n

There is also the concern about keeping a DIY stack up to date with the latest software releases. RedLine13 manages this as well, keeping testing software, operating systems, and dependencies updated with the latest releases and security fixes.<\/p>\n

<\/a>Integrating with AWS<\/h3>\n

There are multiple cloud providers supplying commodity compute instances. Utilizing these resources has become the de facto<\/em> standard in cloud-based load testing. When tasked with a DIY approach, it is up to the test administrator to provision and configure these instances, run tests, collect results, and ultimately dispose of these resources. This can add a significant amount of work to a load testing project. It also adds complexity which can require some degree of the testing of the test architecture itself. Though it confers the advantage of flexibility, taking this approach can increase time and cost.<\/p>\n

Often complexity, time, and cost are sought to be minimized. RedLine13 can help testers achieve this by providing a vetted platform which tightly integrates with AWS. Running a JMeter test on RedLine13 is as simple as uploading the test file, selecting the number and specifications of the EC2 instances<\/a> to be provisioned, and clicking \u201cStart Test<\/em>\u201d.<\/p>\n

<\/a>Hidden Costs of Load Testing<\/h3>\n

With cloud-based load testing, there are finite resource costs which are known. Primarily these are server costs for running load generators, and associated networking resources. However, with a DIY setup one has to be cognizant of additional hidden costs. A significant investment in infrastructure is required to coordinate load generators and collect results. Similarly maintenance of that infrastructure also requires time and attention in keeping that software up to date with the latest releases and security patches. There are also hidden costs in testing that infrastructure itself to ensure that the results obtained are reliable.<\/p>\n

Comparing this to RedLine13, most of these hidden costs no longer apply. With our service you have access to a vetted platform that does not require you as the tester to address these issues. This allows you or your team to focus on what matters most \u2014 running your load tests.<\/p>\n

<\/a>Convenience Features<\/h3>\n

When developing your own testing architecture, inevitably one would seek to automate common and repetitive tasks. However, this comes only after identifying these repetitive tasks, and then requires a development investment to create these shortcuts.<\/p>\n

RedLine13 has already identified many of these convenience features, which are available on the platform for your use today:<\/p>\n