Forum Discussion
AndyHughes
15 years agoRegular Contributor
Based on some testing I have done, I don't think this is the case. In another of my posts I was getting 'out of memory' errors using a fixed load of 4 but with an interval of 10ms. Based on how I understood this to work, that would equate to an absolute maximum of 400 requests per second (100 blocks of 4 requests), but when I did a similar test at a load of 100 with a 100ms interval (which equates to a maximum of 1000 requests per second) there was no problem.
I think its linked to the number of requests 'running' in the soapUI runner. This climbs hugely as you reduce the interval. What does this represent? I thought the load was supposed to be 'fixed'????? There should only ever be running, the number that you have selected as the load level???? Or am I missing something?
I think its linked to the number of requests 'running' in the soapUI runner. This climbs hugely as you reduce the interval. What does this represent? I thought the load was supposed to be 'fixed'????? There should only ever be running, the number that you have selected as the load level???? Or am I missing something?