JMeter. Changing intensity with Constant Throughput Timer
JMeter is a highly extensible, open-source platform that can help identify performance issues in your application. It is among the most popular tools for performance testing. You can read more about difference between PFLB, LoadRunner and JMeter.
So in JMeter, it is no longer possible to change the intensity, the number of threads and the duration of the test by standard methods after starting the test. However, it happens that the test is already running, but you urgently need to change a parameter (for example, I often forget to indicate the test duration), for which you need to stop the test, set database to the initial state, reboot the cluster, pull the original git commit and so on. Solution: configure and run BeanShell Server. With the help of BeanShell Server one can “play” with the following settings. Let’s illustrate it on the example of intensity change.
Variables
jmeter_loc – the full path to the root jmeter folder
host, port – jmeter’s host and port for the machine, where it is running
bsh_loc – folder, containing bsh-files
new_throughput – new intensity value, op/min
old_throughput – default intensity value, op/min
JMeter configuration and start from the command line
Explanation
In the line «java –jar %jmeter_loc%\lib\bshclient.jar %host% %port% %bsh_loc%\name.bsh %new_throughput%» we call bshclient and indicate, which host and port are opened to the bsh-server, as well as which bsh-script needs a new parameter.
Example solution for a maximum search test
The project profile consisted of 20+ operation, so changing each intensity change manually is not fun. We wanted to find a maximally scalable and parametrized solution, which would allow us to use it for different projects with a different operation amount and from different loading machines.
Let’s illustrate it on the example of intensity change.
In the end we’ve written a “universal” .bat-file to change intensity,
where vals-line contains new intensity values, separated by letter “a”.
name.bsh:
In JMeter load test scenario we add a separate thread group and in it – jsr223-sampler. Constant timer is added to the thread group and the intensity change is fired by it. Base intensity values for each iteration are saved in User Defined Variables.
Function Helper explains, how to use intensity values syntax in Target Throughput.
After the .bat-file has been executed, the command line stays open, so we see that the intensity values have successfully been changed.
And that the command has looked like that:
java -jar C:/Users/User/Desktop/apache-jmeter-5.1.1\lib\bshclient.jar localhost 9000 C:/Users/User/Desktop/apache-jmeter-5.1.1/bsh\name.bsh 1344 2016 2016 240
We observe the intensity change in Transaction per Second:
The intensity has been doubled.
Conclusion
Using the described approach, you can increase and reduce intensity, thread amount and test duration, which saves time and helps to choose the optimal load options.
Related insights in blog articles
What Is Chaos Engineering: Overview

Chaos engineering is a way to test how complex systems respond to unexpected problems. The idea is simple: introduce controlled failures and watch how the system behaves. This helps uncover weak points before they lead to costly outages. An approach that forces you to think about the unexpected, making it easier to build robust, fault-tolerant […]
Continuous Performance Testing

Continuous performance testing is a proactive approach to validating the speed, stability, and scalability of software throughout the development lifecycle. It ensures that applications remain responsive under different loads, providing a smoother user experience and reducing the risk of performance-related issues in production.In this guide, we’ll look at what continuous performance testing actually involves, why […]
Loadrunner vs. Neoload: Which Tool Is Better?

When evaluating performance testing tools, many teams find themselves comparing LoadRunner vs NeoLoad; two powerful solutions trusted by enterprises worldwide. In this article, we’ll walk you through their core features, strengths, and limitations to help you make an informed choice. But that’s not all! We’ll also introduce you to PFLB, a modern performance testing platform […]
K6 vs JMeter: Which Is The Best Tool?

When it comes to performance testing, two of the biggest names, K6 and JMeter, often dominate the discussion. But which one truly fits your testing needs? In this article, we’ll break down K6 vs. JMeter: their features, capabilities, strengths, weaknesses, and critical differences. We’ll also introduce a more advanced alternative, PFLB’s load testing platform, for […]
Be the first one to know
We’ll send you a monthly e-mail with all the useful insights that we will have found and analyzed
People love to read
Explore the most popular articles we’ve written so far
- Cloud-based Testing: Key Benefits, Features & Types Dec 5, 2024
- Best Load Testing Tools for 2025: Top 10 Nov 7, 2024
- Benefits of Performance Testing for Businesses Sep 4, 2024
- Android vs iOS App Performance Testing: What’s the Difference? Dec 9, 2022
- How to Save Money on Performance Testing? Dec 5, 2022