Forum Discussion

AndyHughes's avatar
AndyHughes
Regular Contributor
15 years ago

[Resolved] Running Queued and Discarded?

Hi,

I'm learning what LOADUI can do using the example test detailed in SOAPUI.
http://search.yahooapis.com
I am successfully runninng this as a load test in LOADUI but have a question about the items in the Title. Running, Queued and Discarded.

I'm using a generator that ramps up the load to a rate of 200/sec, but the SOAPUI runner never displays the 'Running' field as anything more than 100. When it hits this limit it then begins queueing things up to a max of 1000 and then starts discarding them.

Is this a limit that's deliberately imposed to stop http://search.yahooapis.com getting hammered, or may it be something to do with the network I am on imposing a limit? Or is there some setting somewhere that lets you specify these limits?

I guess if this happens when testing any WCF service then I have reached a point where ramping it up any further is pointless because everything just 'spills over the edge' and gets discarded.

Thanks

5 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hi!

    Those limits can be specified in the soapUI runner configuration (see screenshot).



    (In the Web Page Runner, these settings are easier to find because they're in the General tab. We'll consider moving the soapUI Runner settings there too.)

    The reason that you're even reaching 100 running requests, provided that you've got a decent connection on your side, is most likely because of Yahoo's rate limiting. We do not recommend users to load test someone else's website. If you want to reach a high throughput safely, I'd suggest putting up a local server and hammering 127.0.0.1

    Hope this helps

    /Henrik
    eviware.com
  • AndyHughes's avatar
    AndyHughes
    Regular Contributor
    15 years ago
    Yeah I did wonder about hitting someone elses website. Maybe best not do that in future.

    Shortly after I posted this query I did find those settings. Thanks. I thought that would sort it but I wanted to really ramp up the concurrent samples or 'running', to a really big number, as big as my service can handle really. So I put a big number in to test it and again it maxed out, but this time at 1000 rather than 100. Is there an upper limit built into the SOAPUI runner?
  • AndyHughes's avatar
    AndyHughes
    Regular Contributor
    15 years ago
    Also, wouldn't the yahoo rate limit make the requests get discarded rather than bumping up the number that are running? Really this is the number I would want to see rise as I test a service which begins to struggle with the number of requests I send to it. My theory being that the more I ramp up the rate, the more the average will climb and consequently the number that are 'running' will climb. But if this number maxes out at 1000 (as it seems to) then I may as well stop the test at that point. (Am I making sense).?

    Thanks
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hello,

    There is also a global Thread limit in loadUI which is shared between different runners and other components. This is by default set to 1000, and this is probably the limit you are hitting. To change this setting, go to the Workspace view and open the settings dialog (wrench icon). Under the "Execution" tab there should be a "Max internal threads" field which you can change.

    As for the Yahoo rate limiter, this would likely instantly return an error page to the client, so the request gets sent properly (it isn't discarded) but it should fail, as long as you are asserting the response content.

    Regards,
    Dain
    eviware.com