How to establish the baselines of LOAD tests using LOADUI ??

Hi!

I would start by reading the documentation, including, but not limited to:

• Your first load test, which show you how to load test a web page.


• Web Page Runner Settings, which explains what Maximum Concurrent Request means (among other things).


• Getting started with Results


• Load testing the post office, describing what counters matters in load testing (TPS alone is useless).

Feel free to get back to us if some question remains unanswered

Regards

Henrik
SmartBear Software

Thanks Henrik,

The article in the link "Load testing the post office" is excellent and a must read for any load tester.It helped me to get a understanding of the basics of load tests.

My question on Max Concurrent request was basically flawed.I just wanted to know if i apply a say X concurrent requests. Does that mean that the web page will handle X concurrent requests/seconds? Just wanted to know the unit of time.

The "Fail on missing value","Fail on mismatching ID" and "sample Id" fields was a query of assertion component rather than statistics.I want to know what are the inputs to these respective fields and what do they signify?

Thanks once again and hope that i get insights into these queries of mine.

iamnewuser wrote:
The article in the link "Load testing the post office" is excellent and a must read for any load tester.It helped me to get a understanding of the basics of load tests.

Thanks for the feedback! We will most likely be integrating that blog post into our documentation this week.

iamnewuser wrote:
My question on Max Concurrent request was basically flawed.I just wanted to know if i apply a say X concurrent requests. Does that mean that the web page will handle X concurrent requests/seconds? Just wanted to know the unit of time.

Hmm, I am assuming that we are still talking about the setting in the component's settings dialog. That setting is just an internal limit for the runner and it does not apply any requests in itself. For example, if you are sending new requests (the Requests metric in the runner's display) faster than your server can complete them (the Completedmetric in the runner's display), the number of concurrently running requests will start increasing (the Runningmetric in the runner's display). Max Concurrent requests is a limit for how high the Running metric can rise -- when this limit is exceeded, new request will not be sent but instead queued (the Queuedmetric in the runner's display).

I realize that we should really explain this (better) in the documentation.

iamnewuser wrote:
The "Fail on missing value","Fail on mismatching ID" and "sample Id" fields was a query of assertion component rather than statistics.I want to know what are the inputs to these respective fields and what do they signify?

Ah ok, Fail on missing value will make the assertion fail if there's no value at all. For example, if you assert ResponseSize to be more than 5000 bytes and an incoming (in the wire) message has no field named ResponseSize (e.g. because the request timed out) -- then this option determines whether to fail the assertion.

SampleID is a concept that lets you limit your assertions to certain URLs (for Web Page Runners) or TestSteps (for soapUI Runners). If blank, the Assertion component will not be limited. I will not dive deeper into this since loadUI 2.0 will handle assertions completely different, and sampleID will not be part of that new solution.

Regards

Henrik
SmartBear Software