Timestamp in the load test log
A member of my project team has asked for some help with a performance test he is trying to do on a web service we are developing. He is using SoapUI to perform load tests and he wants to determi...
Forum Discussion
Hi,
I do not use SoapUI for loadtesting, we use LoadRunner. So I can give you information that might be relevant to finding the bottleneck but will likely be like beating a dead horse since there is most likely functionality built in that will do this task better.
There is a couple of options:
I do not use SoapUI for loadtesting, we use LoadRunner. So I can give you information that might be relevant to finding the bottleneck but will likely be like beating a dead horse since there is most likely functionality built in that will do this task better.
There is a couple of options:
- Insert Load Test assertions with the expected amount of time for each request
[list=2:1fnwcnkt]Add a groovy assertion step to each step that will output to a datasource the average TPS, min, max etc
[list=3:1fnwcnkt]Manually review the test steps when the LoadTest has completed to see where the bottleneck occurs
For discovering exactly where the bottle necks are, use process of elimination. If it's a type of flow where each step is required, load test up to step x and then stop it. Continue adding in the next step until you have reached the bottle neck. If not all parameters are required for the step causing the issue, slowly add more parameters into the step until the bottleneck is found.
By the looks of it, SoapUI's load testing function should be able to identify the bottleneck, the issue might be that you need monitors on your server in order to determine exactly what is causing this issue. I would recommend contacting your development team in order to see if they have any that have been built in already.