Does Loadrunner Web Service protocol reuse connections?
| ♥ 0 |
Is there any caching in data or connections from one iteration to the next for web_service_call() calls in Loadrunner? I know in the http/html protocol under run-time settings, there is an option to cache or not and to treat each iteration as a new session. I assume since web_service_call() is completely independent there would not be any cache or session information kept, correct? The reason for this question is the connections seen on the server side seemed low when running a performance test with web services, with only about 20 connections only going inactive/active as opposed to being reset for a 110 Vuser test running at around 5 transactions/sec on average across 11 groups and method calls (10 vusers per group). But, connection settings would be a server side setting and nothing that can be changed on the controller or generator on how it makes connections, right? I have IP spoofing on as well.
Marked as spam
|
Posted by |
Private answer
The Web Service call opens one or more connections as the call is made and then maintains those connections until a response is received. It then opens a brand new connection for each successive process call. So the answer to your question is YES. Your issue of generating 20 connections for 110 users is an indication that system level concurrency is at appoxiamately 20 concurrent requests. This is quite typical for this type of test. Marked as spam
 Posted by jeffrey-gardner-1 (Questions: 17, Answers: 266) Answered on February 28, 2013 4:08 pm
|