loadUI - fixed rate generator

Hi Claudio!

First of all, 1000 requests per second is a lot. This might be exactly what you want, but just to put this in proportion: Bing handles less than 1000 searches per second and Twitter handles 600 tweets per second on average.

cardagna wrote:
[...] In the setting of the soapUI runner, I found the variable "concurrent request". What is its meaning? How does it relate to the rate of the fixed rate generator?

This variable limits the number of concurrent requests that the soapUI Runner allows to be executing at the same time. When this limit is reached, the runner will start queuing requests. You are free to change this variable to suit your needs.

cardagna wrote:
2 - after launching the tests I need to retrieve the round trip time (i.e., the time from just before sending the request to just after the response has been received by the client) and the transactions per second. Is the round trip time the AVG column and the transactions per second the TPS column of the Table log component?

You mention AVG and TPS columns, which makes me believe that you are using a Statistics Component before the TableLog, is this correct? In that case, you're right about our assumptions -- but we don't encourage using the Statistics Component. Instead, use the Statistics Workbench of loadUI (introduced in this part of the documentation).

Does this help you?

Henrik
SmartBear Software