LoadUI Limits
Hi I've finally got our services hosted on some beefy hardware and started load testing. Everything was going great and I was sending in some pretty hefty volumes (I'm talking in excess of 500 req/...
Forum Discussion
These are my settings:
Workspace
Max internal threads 100000
Max internal thread queue size 10000
Concurrent requests setting on the runner is 10000
Queue size 10000
The number that are 'running' is only ever in the hundreds and nothing is ever 'queued' or 'discarded'.
This leads me to believe that these are just loadui limits imposed and not at all representative of whats happening on the server. Is this right? The server is maxed out at this point so I know it's a hardware limit. But it still doesn't explain why the requests on the runner don't increase. Even if the requests are being queued or discarded either by LoadUI or the server, shouldn't the requests just keep coming and the runner reflect this?
Workspace
Max internal threads 100000
Max internal thread queue size 10000
Concurrent requests setting on the runner is 10000
Queue size 10000
The number that are 'running' is only ever in the hundreds and nothing is ever 'queued' or 'discarded'.
This leads me to believe that these are just loadui limits imposed and not at all representative of whats happening on the server. Is this right? The server is maxed out at this point so I know it's a hardware limit. But it still doesn't explain why the requests on the runner don't increase. Even if the requests are being queued or discarded either by LoadUI or the server, shouldn't the requests just keep coming and the runner reflect this?