From: Alan T. DeKok <aland@freeradius.org>
Date: Wed, 29 Nov 2023 15:25:48 +0000 (-0500)
Subject: more notes on connection starvation
X-Git-Tag: release_3_0_27~52
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=836c14b541c40623b16ff0386198a8a953ffa6c4;p=thirdparty%2Ffreeradius-server.git

more notes on connection starvation
---

diff --git a/raddb/mods-available/sql b/raddb/mods-available/sql
index cfeac63ea8..34ec56509f 100644
--- a/raddb/mods-available/sql
+++ b/raddb/mods-available/sql
@@ -286,6 +286,23 @@ sql {
 		#
 		#  Setting 'max' to MORE than the number of threads means
 		#  that there are more connections than necessary.
+		#
+		#  The setting here should be lower than the maximum
+		#  number of connections allowed by the database.
+		#
+		#  i.e. There is no point in telling FreeRADIUS to use
+		#  64 connections, while the database is limited to 32
+		#  connections.  That configuration will cause the
+		#  server to be "starved" of connections, and it will
+		#  block during normal operations, even when the
+		#  database is largely idle.
+		#
+		#  At the same time, if the database is slow, there is
+		#  no point in increasing "max".  More connections
+		#  will just cause the database to run more slowly.
+		#  The correct fix for a slow database is to fix it, so
+		#  that it responds to FreeRADIUS quickly.
+		#
 		max = ${thread[pool].max_servers}
 
 		#  Spare connections to be left idle