loadrunner How do we calculate number of concurrent users...

[Ravi Goel]

How do we calculate number of concurrent users for a fresh eCommerce application which is not in production? We know the total user base (1,20,0000 users) and number of users who will access the application in an hour say 10,000 users in an hour. So now with how many concurrent users should be test?

 

[Nishi Pathak]

A discussion can be conducted with the client company, that in an hour how many orders or query about the product they get simultaneously. Or how many customers come together at any given point of time. With this some idea can be made. This can be done if the client company is developing the business for the first time online.

 

[Ashwin Nair]

Do a step ramp up load test - increase load slowly - to reach a breakpoint. You can see at what point the system fails. Although I would suggest not to do this before you have a discussion with the client or the app team.

 

[Nishi Pathak]

You can try to find out ,among 10000 users, what sort of users will be accessing the application, like if 100 users would be actual buyers then ,it can be considered as concurrent users for a given time period.

 

[Ravi Goel]

The decision on the concurrent users have to be made to calculate number of Vusers licenses required for load runner, also we dont want to break test the app , we want to have performance goals first and then meet them based on business requirement.

 

[RoHan KoKate]

try to target TPS based test first i.e query the client..how much traffic they are expecting... and then try to scale the users based on TPS...

 

[Karthik Subash Ravindran]

Breakup your requirement into more pieces .. You have to get the inputs on what is the business hours per day ? What is the expected normal load per hour ? What is the expected peak load per hour etc ? Calculate the workload accordingly by interacting with the customer or business . You should not do the stress test unless you derive more info and baselining the numbers .

 

[Ram Lekkala]

Step#1: understand the business usage in users point of view. Step#2: Drill down your core business functionality Step#3: Prioritize your core functionality in users point of view (i.e 100% users will login to the application, but 20% users will access deals page, 20% users will access product catalog, 10% users will access some x page and so on) Step#4: Distribute the users across your business functionality according to priority (core business value to the end user) Step#5: Run a loadtest to see the system behavior in terms of response times, TPS, throughput, and sessions etc.. Step#6: if load test satisfied your SLA's, execute with the same amount of load for prolonged duration (8-10 hrs) to pinpoint any memory related bottlenecks and to prove sessions are maintaining consistently with out any blocks. Step#7: stress test would be preferable to know the extrapolation value.