Maximum requests that a server can handle in parallel

Hi!

I will from now on refer to Transactions Per Second as TPS. TPS is often a better way of measuring server performance than requests that a server can handle in parallel, since it implies that the requests are actually completed, and within a certain amount of time.

First of all, we must remember that knowing the max TPS is not very useful without also knowing the response time (often called Time Taken in loadUI). For example, handling 200

What you want to connect a Fixed Rate Generator to a soapUI Runner (or Web Page Runner depending on your needs), and plot TPS and Time Taken in the Statistics Workbench. You can then adjust the rate of the Generator to see how much your web service can handle.

Since you're using web services, you probably want to start by creating a functional test for them in our other software, soapUI, and then load test that TestCase in loadUI.

Here's a few pointers to get you started:

Getting started with loadUI
http://loadui.org/Getting-Started-with- ... -test.html
http://loadui.org/loadUI-Demo-Movies.html

Load testing soapUI TestCases in loadUI
http://loadui.org/Load-Testing-soapUI-T ... -component

Showing results / statistics
http://loadui.org/Getting-results/getti ... d-new.html
http://loadui.org/Getting-results/getti ... -view.html


Hope this helps! With a little patience you should be on the right track soon enough

Henrik
SmartBear Software