Take the 2-minute tour ×
Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It's 100% free, no registration required.

The AUT is on Android platform which has experienced slowness or long time loading a section's contents (more than 17s). I can notice the app only has long time loading the first time I enter that specific menu, after that moving in / out the menu does not have that high loading time anymore. (Something of cached contents? I am not sure)

From the web service perspective I know that this action to enter the menu contains of 3 separate requests and waiting for feedback from the webservice. That's why I used SoapUI to make a simple load test to confirm this slowness.

However, the result for the load is not promising:

  • max response time: around 20000ms
  • average response time: 500ms/1200ms/5000ms (for each 3 requests)
  • That is just for 50 threads which result in 0 to small percent of time-out errors.
  • If I try to use 400 threads instead (which is a requirement from customer), the timeout errors will be unacceptable (50%)

So, my questions are:

  • Is the slowness on the app a result of the sum of these 3 requests: around 7000ms ~ equal 7s? (It is still way much lower than 17s on real device)
  • Also, does this appear that the web service can not afford a high number (400) of concurrent users in real working environment?
  • Could it be that or am i doing something wrong here?

Thank you. Appreciate all the answers.

share|improve this question
And there is no business logic on the client side that calculates the content to display for the first time? –  dzieciou Jul 14 '13 at 6:52

1 Answer 1

welcome to SQA. One thing that it looks like you are not taking into account is the network speed of the device you are testing on. If you are running load runner on a network that has high internet connection speeds, or more probably is on the same network as the service you're testing, then you will get almost no additional time due to network latency, whereas on a device you will likely see quite a bit.

There are tools that you can use while you're executing load runner to simulate network latency, Load runner may actually have this built in, but I'm not super familiar with the tool.

Lastly, adding network latency to the requests will likely exacerbate the issues you're seeing with timeouts because now the web service will have to wait longer before it gets a response back from the client and will have more threads it's keeping around in memory for a longer period of time.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.