Why Active users number is less...???

Gatling (Open-Source)
1

Hi,

I am new to gatling…I did one simulation for my application…Actually I gave 1000 users and 4000 ramp up…But in the results I am not getting 1000 active users…By seeing the numbers

I confused…whats happening behind the scene???I want to know…And In this how to calculate concurrent users and simultaneous users???For reference I am adding results graphs in text file…

I am not getting any error on console and all requests are passing…But why active user count is less??? please explain in detail…

Simulation results.docx (184 KB)

2

Can you post your Simulation code.

3

setUp(scn.inject(rampUsers(1000) over(4000))).protocols(httpProtocol)

4

Hi there,
Your attachment said the load injection was “Setup used ------------:setUp(scn.users(1000).ramp(4000).protocolConfig(httpConf)”
which is gatling 1 syntax, and different from the line you just provided. So I have little confidence currently that the results page comes from the latest version of Gatling.

Can you rerun your test and provide the results page with the latest version of gatling, please?
stating which version of gatling you ran.
providing the console output would be of use also.

thanks,
Alex

5

Sorry,For confusion…wat ever I gave for gatling 2 is correct one…Please give me solution based on that…

6

In order for you to see 1000 active users, each user must continue to run for the duration of the test. With a ramp of 4000, each user must keep running for at least 4000 seconds. You will need to use some kind of looping in your scenario.

7

John,Thanks for the response…but to see 1000 active users I have to loop the simulation 1000 times or what is the way??I am in confusion…So please explain with example code…And there are lot of looping concepts in gatling…So which one will be adoptable for this scenario??How active users concept is there is gatling please explain in the internal architecture…please help…

8

Gatling 101:

If your “scenario” is one transaction, and that transaction takes 1 second, then the whole thing is finished in 1 second.

If you inject 50 users over 50 seconds, you will never have more than one active user at a time.

In order to have 50 users active at the same time, the users must be long-running. You can make them long running by simply adding a loop. The simplest way to do this is to use “during”

val scn = scenario ( "name" ) .during( 60 seconds ) { // target running time + ramp time is best // do your stuff here - without the initial "." for the first exec() }

The documentation is not as user-friendly as it could be for total newbies, I admit. All in due time. But take the time to read it and understand it, and you won’t be as frustrated.

9

Thank you so much john…its working…