Concurrent users low than expected in the scenario
See original GitHub issueHi, My scenario is :
phases:
- duration: 300
arrivalCount: 50
arrivaleRate: 10
I’m trying to test with constant 50 users and I followed this solution #353
But why in Concurrent users graph I see that the max count is 6 ( y_accessor ) ?
Any one could help ? is that a bug or does this concurrent users means something else ?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Determining Concurrent Users from Web Analytics - LoadView
This is important for a couple of reasons. Using the average traffic metrics will often be significantly lower than peak times.
Read more >How do I Correlate the Number of (Concurrent) Users with Hits ...
Selecting the correct number of Concurrent Users is pretty easy. However, when you have a certain amount of hits/s (Hits per second aka...
Read more >JMeter - 350 Concurrent Users load testing fails due to ...
So I'm performing load test for the registration scenario and when I perform load test with JMeter for 350 concurrent users using Thread ......
Read more >Load Testing Basics: How Many Concurrent Users is Enough?
The key to understanding this calculation is the concept of levels of concurrency. If a user spends on average 10 minutes on a...
Read more >Loadrunner: Understanding Transaction Per Second (TPS)
Number of concurrent users and TPS go side by side. So it is important to consider both while setting up load test scenario....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You’re asking for 50 users to arrive over 300 seconds. How many of them will be concurrently executing depends on their scenarios. Think of it like this: there’s a supermarket. 50 people go in over the period of an hour. How many people will be in the shop at some point in time N? That depends on how much time they’re spending inside. It could be 20, it could be 5, and it could be 0.
@hassy I got you, thanks. but it would be better like if Im asking for 50 to be concurrently running, it should run it and if it can’t it should break or ask to decrease the concurrent users so that we can know exactly how our app handles a specific number of concurrent users. Are you planning to make this update in any near future ?