I use this load model:
`
setUp(scn.inject(rampUsers(500) over (100 seconds))).protocols(httpConf)
`
with during like this:
`
val scn = scenario(“Scenario”).during(700 seconds){
`
and I get this in my console:
`
Yes, it looks like your system can’t handle more concurrent users. The reason really depends on your architecture. The most current reason is database connections starvation.
Ok, thanks, I might add that I only have 13 users to test with at this time, and this is all the users that exists in the database.
That might be a problem in itself? That when adding this many users and only having a population of 13 userIds to choose from it might create this kind of ‘bottleneck’?
What is connections starvation in this context?
Thanks,
Magnus
Ok, thanks, I might add that I only have 13 users to test with at this
time, and this is all the users that exists in the database.
That might be a problem in itself? That when adding this many users and
only having a population of 13 userIds to choose from it might create this
kind of 'bottleneck'?
Honestly, can't say without work on the application myself/consulting.
What is connections starvation in this context?
I meant something like JDBC connection pool starvation (all connections are
borrowed, so incoming requests have to wait for one to be available).
Ok, consulting might be interesting. The app (read web-services) is also ‘live on the internet’.
Do you have a mail adr. where we can discuss this in more detail?
Magnus