DOC: explain the relation between pool-low-conn and tune.idle-pool.shared
authorWilly Tarreau <w@1wt.eu>
Fri, 19 Feb 2021 10:45:22 +0000 (11:45 +0100)
committerWilly Tarreau <w@1wt.eu>
Fri, 19 Feb 2021 10:49:04 +0000 (11:49 +0100)
commit0784db8566b5c4eea5b18bf533ef978a1909b97a
tree3568b9a145de6cf917c0290523dacb0b33e82983
parent4cce7088d1a7b7ac28966686088f6d2478286f12
DOC: explain the relation between pool-low-conn and tune.idle-pool.shared

Disabling idle-pool sharing can result in awful performance in presence
of a not so high number of threads, because the number of available idle
connections will be shared among threads, resulting in most of them
abandonning their connections after a request is done if there are already
enough total available. This is a case where pool-low-conn ought to be
used to preserve a number of connections for each thread, but this relation
isn't obvious as is. Let's add mentions about this with both keywords.
doc/configuration.txt