Remove idle_pool_size config

Clients created when idle_capacity is reached but not max_capacity
are discarded as soon as the client is checked back into the pool,
not when the connection is closed.

This means that allowing idle_capacity to be lower than max_capacity
essentially just makes the remaining clients a checkout timeout
deterrent that gets thrown away as soon as it is used. Not useful
for reusing connections whatsoever during peak load times
This commit is contained in:
syeopite
2025-04-10 00:42:43 -07:00
parent 24a6c31b18
commit 0865bc55fd
4 changed files with 1 additions and 31 deletions

View File

@@ -214,25 +214,6 @@ https_only: false
##
#pool_size: 100
##
## Max idle size of the HTTP pool used to connect to youtube. Each
## domain ('youtube.com', 'ytimg.com', ...) has its own pool.
##
## This means that when releasing a connection back into the pool, it will
## be closed if there are already more than idle_pool_size connections within
## the pool
##
## Do note that idle connections are kept around forever without any way of
## timing them out.
##
## When unset this value has the same value as pool_size
##
## Accepted values: a positive integer
## Default: <none> (internally this means that it has the same value as pool_size)
##
#idle_pool_size:
##
## Amount of seconds to wait for a client to be free from the pool
## before raising an error