Getting the number of currently tracked requests
Hello, I am trying to find a way to get the number of currently tracked connections by FreeRADIUS (2.2.1) in order to size my max_requests. Is there a way to get that information from radmin or some other tool? I realize I can always set it to some value based on the number of clients and just see if there are warnings in the logs about max_requests being too low but I would like to monitor the number of requests to tune FR as much as possible. If the same method works for other values (such as the current queue_size ) that would be a bonus. Regards, -- Louis Munro
Louis Munro wrote:
I am trying to find a way to get the number of currently tracked connections by FreeRADIUS (2.2.1) in order to size my max_requests.
In 2.x, not really. We're looking into adding that for 3.x
I realize I can always set it to some value based on the number of clients and just see if there are warnings in the logs about max_requests being too low but I would like to monitor the number of requests to tune FR as much as possible.
Just set it to a large number. It's 2014, and your systems should be massively over-provisioned with memory. If you set max_request = 1000000 Then FR won't use any more memory than with it set to "1024". The only difference is that when something goes wrong, it will take more time for the server to discover that it's melting down. Alan DeKok.
On 2014-03-03, at 11:11 , Alan DeKok <aland@deployingradius.com> wrote:
I realize I can always set it to some value based on the number of clients and just see if there are warnings in the logs about max_requests being too low but I would like to monitor the number of requests to tune FR as much as possible.
Just set it to a large number. It's 2014, and your systems should be massively over-provisioned with memory. If you set
max_request = 1000000
Thank you. Point taken about today's systems. I was wondering if something like the following might work. (gdb) call fr_packet_list_num_elements(pl) I could stick it into a file and call gdb in batch mode. But I am a gdb novice and I am wary of any side-effects, especially regarding performance. The point would be to monitor the size of the queue as it grows or shrink across time, mostly to see how it correlates with other metrics (e.g. database latency). I would stick the return value in a database (something like an rrd maybe) and see how it evloves. While it might not be relevant to actual capacity planning, I though it could be useful to graph that queue size. What do you think? Regards, -- Louis
Louis Munro wrote:
On 2014-03-03, at 11:11 , Alan DeKok <aland@deployingradius.com I was wondering if something like the following might work.
(gdb) call fr_packet_list_num_elements(pl)
Yes, but it would be a very bad idea. Going to the gdb command-line will stop the server entirely. You're MUCH better off patching the server to make the stats available via radmin.
I could stick it into a file and call gdb in batch mode. But I am a gdb novice and I am wary of any side-effects, especially regarding performance.
It will kill performance. Alan DeKok.
participants (2)
-
Alan DeKok -
Louis Munro