LoadUI/SoapUI Throttling Requests?
I'm wondering if my issue is the same as the problem identified by the post "loadUI only injects 2 requests simultaneously ?!" submitted by opstalj on April 25th, 2012.
I am seeing different LoadUI results depending on the SoapUI version I use (at least that is the only difference I can identify). Using LoadUI 2.0.1 if I test with SoapUI 4.5.0 all seems to work fine with my load testing and results are as expected. We run 20 requests per second (fixed rate) and after 1 minute our application processes approximately 1200 requests. While LoadUI is running, the "Running" queue never really goes above 20 requests and none get queued. But with SoapUI 4.5.1, we only process about 895 requests in that same time period. When running the test, the "Running" queue maxes out at 100 and many end up being queued (in the hundreds). The two sets of tests (i.e. running one test with LoadUI 2.0.1/SoapUI 4.5.0 and then with LoadUI 2.0.1/SoapUI 4.5.1) are run back to back against the same web service that we are testing - so no difference in the web service code version that each one hits. I have compared the configurations and settings and everything looks the same. The only difference I see is using the different version of SoapUI. So I'm wondering if this is the same issue as described by post I listed above and that in the first instance where it seems to work for us it is really because it is just being throttled by the bug in SoapUI 4.5.0?
I am seeing different LoadUI results depending on the SoapUI version I use (at least that is the only difference I can identify). Using LoadUI 2.0.1 if I test with SoapUI 4.5.0 all seems to work fine with my load testing and results are as expected. We run 20 requests per second (fixed rate) and after 1 minute our application processes approximately 1200 requests. While LoadUI is running, the "Running" queue never really goes above 20 requests and none get queued. But with SoapUI 4.5.1, we only process about 895 requests in that same time period. When running the test, the "Running" queue maxes out at 100 and many end up being queued (in the hundreds). The two sets of tests (i.e. running one test with LoadUI 2.0.1/SoapUI 4.5.0 and then with LoadUI 2.0.1/SoapUI 4.5.1) are run back to back against the same web service that we are testing - so no difference in the web service code version that each one hits. I have compared the configurations and settings and everything looks the same. The only difference I see is using the different version of SoapUI. So I'm wondering if this is the same issue as described by post I listed above and that in the first instance where it seems to work for us it is really because it is just being throttled by the bug in SoapUI 4.5.0?
