14 years ago
Poor performance with SoapUI Runner vs Web Page Runner
Hello Smartbears,
I have a simple LoadUI test suite that has a fixed load generator (40 users), and a soapUI runner.
If I run that (the soapui runner does a rest/json get) via SoaUI runner I get ~ 20tps per loadui-client. So if I have 12 clients I get 140 tps. I have tried adding clients and the improvement is always around 20tps per loadui-client...
So I tried making the same call using web page runner and I get much better performances.. now I get ~ 1000 tps and I can lower the number of loadui-clients (too a point) and I see the same performance.
I also need to simulate clients calls that are rest/json via POST, but I can't do that with the webpage runner.
So any ideas how to break though this loadui imposed bottleneck?
Thanks,
John.
I have a simple LoadUI test suite that has a fixed load generator (40 users), and a soapUI runner.
If I run that (the soapui runner does a rest/json get) via SoaUI runner I get ~ 20tps per loadui-client. So if I have 12 clients I get 140 tps. I have tried adding clients and the improvement is always around 20tps per loadui-client...
So I tried making the same call using web page runner and I get much better performances.. now I get ~ 1000 tps and I can lower the number of loadui-clients (too a point) and I see the same performance.
I also need to simulate clients calls that are rest/json via POST, but I can't do that with the webpage runner.
So any ideas how to break though this loadui imposed bottleneck?
Thanks,
John.