You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I would like to enquire about some connection pool parameters:
I saw that MaxActiveConns was introduced back in v9.2.0. From my understanding, any connections that are created within the set of MaxActiveConns - MaxIdleConns are considered as 'short' connections, i.e. these connections are closed immediately after used instead of being placed back into the pool. Short connections may potentially add extra load to the Redis nodes and overwhelm the nodes since repeatedly creating and closing connections can be expensive for the Redis nodes. May I know what is the rationale behind introducing MaxActiveConns?
May I know why is PoolTimeout default to ReadTimeout + 1 second?
May I know why is PoolSize default to 10 * runtime.GOMAXPROCS ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi! I would like to enquire about some connection pool parameters:
I saw that
MaxActiveConns
was introduced back in v9.2.0. From my understanding, any connections that are created within the set ofMaxActiveConns - MaxIdleConns
are considered as 'short' connections, i.e. these connections are closed immediately after used instead of being placed back into the pool. Short connections may potentially add extra load to the Redis nodes and overwhelm the nodes since repeatedly creating and closing connections can be expensive for the Redis nodes. May I know what is the rationale behind introducingMaxActiveConns
?May I know why is
PoolTimeout
default toReadTimeout
+ 1 second?May I know why is
PoolSize
default to 10 *runtime.GOMAXPROCS
?Thank you in advance!
Beta Was this translation helpful? Give feedback.
All reactions