jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 62352] New: Load test throughput halved in\by Jmeter 4.0
Date Fri, 04 May 2018 11:48:51 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=62352

            Bug ID: 62352
           Summary: Load test throughput halved in\by Jmeter 4.0
           Product: JMeter
           Version: 4.0
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: jehan.coetzee@hotschedules.com
  Target Milestone: ---

Created attachment 35911
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=35911&action=edit
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

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

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