Hi, This is the request that radius performs. TLS is not used. The connection is taken from the pool to locality Authentication delays are not a database problem. <Start of Query> THIS IS THE NUMBER YOU HAVE <End of Query> Alan says that this is where the problem is. Redards, Sergey Kodentsev. On 27.05.2025 12:52, Winfield, Alister (Senior Solutions Architect) via Freeradius-Users wrote:
That’s not the query that FreeRADIUS is performing, so you are seeing stats that don’t help. Query time is the time from query receipt to query result NOT the overall time which includes connection delays, TLS delays and authentication delays.
You are missing.
<FR needs to do a query> <Highly likely pool is exhausted so.> Time to resolve hostname of DB Time to connect to DB socket Time for TLS exchange (Assuming encrypted comms). Time to authenticate to DB
<Start of Query> THIS IS THE NUMBER YOU HAVE <End of Query>
Time for result set to get to the RADIUS server <here FINALLY FR gets to do something with that result>
You need the WHOLE time taken