Interested to Buy Any Domain ? << Click Here >> for more details...
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
What is ms-windows?
During the load test, what is the optimum setting for logs?
When loadrunner is used?
How many types of vuser are available?
When a scenario run exactly what happened?
What is the configuration of systems when using load runner?
What is the difference between lr_error_message and lr_debug _message?
Why we insert the rendezvous point while running the scenario?
How can correlation be performed?
What do you mean by initialization of quota?
What is the think time? What is the threshold level for think time and how can be this changed?
What protocols does loadrunner support?
what are the risks you faced with loadrunner
Why do you create parameter?
What is the difference between transaction and transaction instance in loadrunner ?
