Forum Discussion

mtan2014's avatar
mtan2014
Occasional Contributor
12 years ago

Load UI summary

Hi, I ran a distributed load test and from the summary it wasn't showing correct numbers. The test contained 3 scenarios. A scenario contains a generator (30/s), a soap ui runner and 3 logs co...
SmartBear_Suppo's avatar
SmartBear_Suppo
Icon for Alumni rankAlumni
12 years ago
Hello,
Ill try to address your problems one at the time below.

    1. Inconsistent numbers in summary report
    The inconsistent numbers you are seeing might be due to requests being discarded. If they are they should show up in the discarded counter in the Runner. I would like you to send me screenshots of the numbers you are talking about so i can fully understand the problems you are having.

    2. Table Log components being empty
    The logs being empty might indicate that the requests failed, have you tried connecting a log to the fail output(left most terminal)?

    3. Setting the generator to 240/s but only getting 120/s in the test.
    This is a strong indicator that the requests are being discarded.

    This could mean one of three things

      1 - Your machine is not being able to generate all the requests.
      Symptom: High LoadUI CPU usage.
      Solution: distribute the test to agents to be able to generate the amount of user you need.

      2 - The tested server cant handle more than a arrival rate of 120/s
      Symptom: The server is starting to take longer and longer time to respond(and eventually not responding at all)
      Solution: no solution here, You have found the limit of what the server can handle!

      3 - You are reaching more than 100 concurrent users
      Symptom: If the running counter in the is reaching 100 without the response time of the server going up.
      Solution: Raise the "Max concurrent requests" value in the Advanced tab in the SoapUI settings.


    4. The Table log is not logging anything when running a distributed test.
    To enable this just check the enabled in distributed mode check box in the table log. NOTICE: this causes each entry being sent individually over your network. In large tests with high rates this might cause a big strain on your computer and network. We advice you to only use this feature for small tests or debugging.

    5. Assertion failures.
    Yes, from your description it sounds like all your requests failed. If they failed as assertion errors it means the assertion in SoapUI failed.


Did i cover everyhing? Any questions?

Regards,
Max
LoadUI Developer