Forum Discussion

soapuinewb's avatar
soapuinewb
New Contributor
12 years ago

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 determine where speed is reduced in the process, ie. is it the network that is slow or the actual request. He is already logging the duration of the request to response from ESB to the DB along with a timestamp of that request. So now he wants to log the data in the SoapUI load test 'Last' column along with a timestamp so he can compare the values at the exact time they occured. He can see the values constantly changing when he runs the test and can see those values in the log extract from the load test graph, but there is no timestamp for each request submission.

I'm hoping someone can help suggest how we can do this. Or maybe suggest another way of using SoapUI to verify where the bottleneck is when submitting a request.

I have no performance testing experience so I hope this question makes sense.

2 Replies

  • PaulDonny's avatar
    PaulDonny
    Regular Contributor
    12 years ago
    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:

      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.
  • soapuinewb's avatar
    soapuinewb
    New Contributor
    12 years ago
    Thanks for your advice PaulM. I'll pass the info on to my team mate.