You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Just want to ask a question. Does the stats.main.meter.mean refer to the number of requests per second the server was able to do? Because the word you used on the page was iterations per second, so i don't really know if they are the same thing.
Thanks
The text was updated successfully, but these errors were encountered:
I used the term iterations rather than requests per second since it is referring to the whole sequence of requests in the main part of your flow.
So if you only have a single request in the flow it, then an iteration / sec == requests / sec.
If you have more than one operation (or request) in your flow then it represents the number of times per second that all those operations were executed. Also note that it only is referring to the iterations in the main section, not any before or after iterations which are basically setup and teardown operations that are excluded from the measurement.
IN this case we have a put and a get operation making up an iteration.
Thus if we are doing 100 iterations / second it means we have done 100 puts and get combinations per second. Thus if you want pure requests / second you would multiply iterations by number of requests, meaning it would be 200 requests / second.
If you have only 1 operation in your flow then iterations == requests.
Let me know if this helps explain it better or you still have questions.
Hi,
Just want to ask a question. Does the stats.main.meter.mean refer to the number of requests per second the server was able to do? Because the word you used on the page was iterations per second, so i don't really know if they are the same thing.
Thanks
The text was updated successfully, but these errors were encountered: