RadPerf failed requests explanation
I'm using RadPerf to test our servers for 10k auth requests in 10 requests in parallel. The server used python module and sql, and performs around 285 packets/s accepting all the 10k requests but there are times when there are several failed requests around 5 to 20. Why are there failed requests? From RadPerf README file, Performance testing ------------------- To see the maximum accepted load that a RADIUS server can handle, use: $ radperf -p 100 -s -f test.csv ... Using larger values for -p will not change the maximum accepted load, but will change the delay between a request and response.
"Using larger values for -p will not change the maximum accepted load, but will change the delay between a request and response" Why is that?
On Feb 5, 2016, at 1:08 AM, Jim <jbalatero@visp.net> wrote:
"Using larger values for -p will not change the maximum accepted load, but will change the delay between a request and response" Why is that?
A RADIUS server can only process a limited number of packets per second. If you overload it, the incoming packets will be queued for later processing. The time that the packet spends n the queue adds to the delay in response. Alan DeKok.
participants (2)
-
Alan DeKok -
Jim