Answer Posted / mahesh sv
In Running Vuser graph correlated with the response time
graph you can see that as the number of Vusers increases,
the average response time of the check itinerary transaction
very gradually increases. In other words, the average
response time steadily increases as the load
increases. At 56 Vusers, there is a sudden, sharp increase
in the average response
time. We say that the test broke the server. That is the
mean time before failure (MTBF). The response time clearly
began to degrade when there were more than 56 Vusers running
simultaneously.
| Is This Answer Correct ? | 1 Yes | 0 No |
Post New Answer View All Answers
When the loadrunner controller open the winrunner file then what is the location of the winner configuration file?
What kind of problem we can face regarding hardware, software, network and memory bottleneck during the performance test?
How does caching affect performance testing results?
How can we edit the vuser script?
What are the changes that can be made to run-time settings?
Which components have you used in loadrunner ?
How can correlation be performed?
How will you stop the execution of a script on error?
How many types of graphs are available in loadrunner?
What are all the reasons to use the server resources monitor?
how to add 100 for dynamic(correlate value) value
What is the rendezvous point?
How many vusers are required for load testing?
What is the basic credentials should be provided while recording SAP-GUI?
Difference b/w 9.1 and 9.5 Versions in LoadRunner?