the Max number of users mentioned in BlazeMeter Report Summary is not showing correctly
Article ID: 217281
Updated On:
Products
Issue/Introduction
we are facing an issue wherein, we have triggered a run today in which we have provided load configuration which the number of users mentioned in BlazeMeter is not showing correctly
(VU users in BlazeMeter = 15 and it's showing 4 or 5).
Please have a look into this and kindly provide us the solution to fix this issue.
Environment
Release : SAAS
Component : BLAZEMETER PERFORMANCE TESTING
Cause
The JMeter script had two thread groups set up.
1 for 5 users and one for 10 users.
Test Plan Setup:
Thread group 1
Thread group 2
They were set to run Consecutively
The first thread group would take up about 9 minutes and the second thread group only had about 1 minute before the test ended.
Resolution
The JMeter script for the test is configured with two thread groups to run consecutively.
the first one has 5 users and the second one has 10 users.
The BlazeMeter Test is configured to have a 1 minute ramp-up time and then 9 minutes of total run time before it ends.
When we look at the Jemeter.log files for each engine running we can see that the first thread group completes in just about 9 minutes.
This leaves the second thread group about 1 minute to startup before the test is ended.
We see this by the thread group entries in the logs:
First thread group
Line 55: 2021-06-08 07:54:17,185 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-ThreadStarter 1-1
Line 114: 2021-06-08 07:54:33,051 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-ThreadStarter 1-2
End of First thread group:
Line 4528: 2021-06-08 08:03:40,502 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-ThreadStarter 1-92
Line 4577: 2021-06-08 08:03:46,823 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-ThreadStarter 1-93
start of second thread group:
Line 4586: 2021-06-08 08:04:04,725 INFO o.a.j.t.JMeterThread: Thread started: bzm - Concurrency Thread Group-ThreadStarter 2-1
The configured users in the 2 thread groups were overridden so that when the test was deployed to 4 locations, the Number of Threads (users) was changed to 1 (from 5) for the first thread group on all 4 locations.
The Target Concurrency was changed to either 3 or 2 on the 4 locations (so there was a total of 15 users configured in the test).
The distribution of users over thread groups is explained in the "Total Users" section of the "Load Configuration" article -
Load Configuration – BlazeMeter
the reason you see a Max Users of 4 on the Summary page is that only 1 user was configured in the first thread group on 4 locations (not 5 users on each location).
Suggested Solution:
I would suggest that you configure the duration in the JMX script itself and disable the Duration in the Load Configuration section of the test in BlazeMeter.
Also, Please review the difference between Max users and Total users.
Below is an article explaining this difference.
Max Users vs. Total Users -- Did All My Users Run? – BlazeMeter
Additional Information
Attachments
Feedback
