Load test throughput cut by half in Jmeter 4.0

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Load test throughput cut by half in Jmeter 4.0

Walker Mellema-2
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

Where would I report a bug like this?

Thanks.


--
Walker B. Mellema  |  Senior QA Engineer  |  ​415.420.5513
Reply | Threaded
Open this post in threaded view
|

Re: Load test throughput cut by half in Jmeter 4.0

Felix Schumacher
Am 03.05.2018 um 19:39 schrieb Walker Mellema:

> 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
>
> Where would I report a bug like this?
If you can share the test plan, you could file a bug in bugzilla as
described on http://jmeter.apache.org/issues.html or you could discuss
the elements used in the testplan here.

Regards,
  Felix
>
> Thanks.
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Load test throughput cut by half in Jmeter 4.0

Philippe Mouawad-2
In reply to this post by Walker Mellema-2
Hello,
Are you using 3rd party plugin ?

Can you attach to your bug jmeter.log, the process information (ps -eaf |
grep jmeter) , the test plan if possible and any third party component
you’re using.

Thanks

On Thursday, May 3, 2018, Walker Mellema <[hidden email]>
wrote:

> 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
>
> Where would I report a bug like this?
>
> Thanks.
>
>
> --
> Walker B. Mellema  |  Senior QA Engineer  |  ​415.420.5513
>
Reply | Threaded
Open this post in threaded view
|

Re: Load test throughput cut by half in Jmeter 4.0

Philippe Mouawad-2
Hello,
You opened for this:

   - https://bz.apache.org/bugzilla/show_bug.cgi?id=62352

From what you describe :

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


If you're using JSR223 Test elements, then issue would be explainable as
you have:

   - in Test 3, saved your file with 4.0 format and opened it in 3.3 which
   is not upward compatible ( JMeter is only backward compatible). If using
   JSR223 Test Element with "Cache compiled..." checked, it would become
   unchecked in 3.3
   - In Test 4, did you use the JMX as in Test 3 or did you use it after
   saving it again in 3.3 ?


In order to move forward, could you provide elements requested in bugzilla ?

Thanks

On Thu, May 3, 2018 at 8:27 PM, Philippe Mouawad <[hidden email]>
wrote:

> Hello,
> Are you using 3rd party plugin ?
>
> Can you attach to your bug jmeter.log, the process information (ps -eaf |
> grep jmeter) , the test plan if possible and any third party component
> you’re using.
>
> Thanks
>
> On Thursday, May 3, 2018, Walker Mellema <[hidden email]>
> wrote:
>
>> 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
>>
>> Where would I report a bug like this?
>>
>> Thanks.
>>
>>
>> --
>> Walker B. Mellema  |  Senior QA Engineer  |  ​415.420.5513
>>
>


--
Cordialement.
Philippe Mouawad.