Forum Discussion

amehra's avatar
amehra
Occasional Contributor
12 years ago

LoadUI report statistics issue

Hi,

Scenario :
I am using LoadUI 2.5.4 to test a webservice. The webservice is hosted on a linux box and i am running LoadUI through my windows 7 machine.
I have around 10 soapUI runners in my LoadUI project and i run them all in parallel. I run for request limit of 1000.
The run completes in under 3 minutes and I generate a report giving minimum,maximum and average response times of each soapUI runner.

Problem :
1. The numbers given in LoadUI report are way above from what I get from the logs of the service. I log the start and end times of each request in the logs and i also monitored manually the start and end time of these 1000 requests. How can I get correct times captured in the report?
Can somebody share if they have faced similar issues? And any solution for this?

2. Another problem faced is, when i do a re-run of the above scenario LoadUI hangs after sending few requests like 500-600 and never recovers. Is there issue with memory?
Any solutions?
I run this on a 8 GB ram , Intel i5 2.6 GHz Dual core processor with 64-bit Windows 7 on it.

Thanks,
Amit
  • Hi!

    2. To find out if it's a memory issue, you can increase the allowed memory for LoadUI by modifying loadUI.bat, and then starting LoadUI using loadUI.bat. You want to try setting Xmx to a higher value by changing Xmx1024m (1024 MB) to something higher.

    So this row in loadUI.bat:
    set JAVA_OPTS=-Xms128m -Xmx1024m -XX:MaxPermSize=256m

    ...should be changed as follows (for example):
    set JAVA_OPTS=-Xms128m -Xmx2000m -XX:MaxPermSize=256m


    LoadUI 2.6 (scheduled for release July 31) includes a System Log which contains error messages in cases like this, which makes it much easier to troubleshoot.

    Please keep us updated on this!

    Henrik O
    SmartBear Software
  • 1. I've not heard of such issue. Keep in mind that LoadUI measures from the client side. By default, it measures this:
    Any SoapUI TestSteps prior to the server request + Client network (software+hardware) interface + Network latency for response + Server network interface + Web Server processing time + App Server processing time + Server network interface + Network latency for response + Client network interface + Any TestSteps after the server request

    While your server is probably measuring this:
    App server processing time

    or this (depending on where you get your measurements from:
    Web Server processing time + App Server processing


    Regards

    Henrik O
    SmartBear Software
  • amehra's avatar
    amehra
    Occasional Contributor
    Thanks for your timely reply Henrick.

    1. I increased the size as mentioned by you in loadUI.bat and currently it looks like this :
    set JAVA_OPTS=-Xms128m -Xmx2048m -XX:MaxPermSize=256m

    I then ran the .bat file but it did not start loaduI. I had to instead start LoadUI via the normal route, using the .exe file.
    I tried stimulating my scenario but it again hanged at 600 odd requests. Not sure what is the issue here :/

    2. Thanks for the insight on this. As i can see, the big time differences can only be due to network latency, will try to run it via different networks.

    Thanks,
    Amit
  • amehra wrote:
    1. I increased the size as mentioned by you in loadUI.bat and currently it looks like this :
    set JAVA_OPTS=-Xms128m -Xmx2048m -XX:MaxPermSize=256m

    I then ran the .bat file but it did not start loaduI. I had to instead start LoadUI via the normal route, using the .exe file.
    I tried stimulating my scenario but it again hanged at 600 odd requests. Not sure what is the issue here :/

    Do you know how many requests that were running concurrently at this point? Would it be possible for you to share your SoapUI TestCase(s) or a screenshot of it/them?

    Henrik O
    SmartBear Software