Forum Discussion
SmartBear_Suppo
13 years agoSmartBear Alumni (Retired)
Hi,
To generate 14 requests per second, or 140 requests per second, you should use a Fixed Rate Generator (set to either 14 or 140 requests per second). This will use as many Threads as required (without exceeding the max number of threads in the configuration) to send the desired number of requests. It's quite possible that this won't get you 14 or 140 requests processed per second, but this would be either due to your client not being able to generate enough load (not very likely, as both of these values are relatively low), or that your server isn't able to process the requests fast enough (much more likely, depending on how much work the server has to do per request). If this is the case, you should be able to see this by looking at the different numbers of the Runner: The Running count will likely max out and stay at the max number of concurent requests (100 by default), and the Queued counter will start to increase. Once the Queued counter reaches its max, requests will start being Discarded. If this is happening, it means that the server isn't able to respond to all the requests, and increasing the rate, or the allowed number of Threads will likely only worsen the performance of the server.
Regards,
Dain
eviware.com
To generate 14 requests per second, or 140 requests per second, you should use a Fixed Rate Generator (set to either 14 or 140 requests per second). This will use as many Threads as required (without exceeding the max number of threads in the configuration) to send the desired number of requests. It's quite possible that this won't get you 14 or 140 requests processed per second, but this would be either due to your client not being able to generate enough load (not very likely, as both of these values are relatively low), or that your server isn't able to process the requests fast enough (much more likely, depending on how much work the server has to do per request). If this is the case, you should be able to see this by looking at the different numbers of the Runner: The Running count will likely max out and stay at the max number of concurent requests (100 by default), and the Queued counter will start to increase. Once the Queued counter reaches its max, requests will start being Discarded. If this is happening, it means that the server isn't able to respond to all the requests, and increasing the rate, or the allowed number of Threads will likely only worsen the performance of the server.
Regards,
Dain
eviware.com