jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 62352] Load test throughput halved in\by Jmeter 4.0
Date Sun, 13 May 2018 21:16:31 GMT

--- Comment #3 from Philippe Mouawad <> ---
(In reply to Jehan Coetzee from comment #0)
> Created attachment 35911 [details]
> Results
> Our load tests recently began running at half the normal rate. Response
> times were slightly longer, but the requests per minute had dropped to half
> the expected rate. We're running Java 8.
> Our load tests were written in Jmeter 3.3. After some investigation we
> found that opening a Jmeter 3.3 file with Jmeter 4.0 and saving it
> (converting it to 4.0) was the culprit. The test runs at twice the rpm in
> Jmeter 3.3 vs. the SAME jmx file saved in 4.0
> I ran 4 tests and the results are described below and attached.
> Test 1 : ran the test with Jmeter3.3 
> Test 2 : ran the test with Jmeter4.0
> These two test yield the same results in terms of throughput, response time
> and error rate
> Test 3 : I then opened the .jmx in Jmeter4.0 and saved it again . Not making
> any changes to it, but now it is a "Jmeter4.0" test. I then ran the test in
> jmeter 3.3

Doing this is wrong, JMeter never guarantees upward compatibility.
As an example, if your test uses JSR223 Test Element with "Cache compiled"
checked, by doing what you describe 
you would end up in 3.3 with this unchecked because XML saving format has

> This is where it gets interesting; the throughput was now half of the
> throughput achieved in the first two tests.
> Test 4 : I ran the same test (as in Test3) again in Jmeter4.0, again the
> test only produced half the original throughput

If you have JSR223 Test Element, then it would also be explainable.

Please note that if we don't get any feedback within 7 days, we'll be closing
this ticket.


You are receiving this mail because:
You are the assignee for the bug.
View raw message