feat(redis): configurable connection pool size - #1055
Open
alexluong wants to merge 1 commit into
Open
Conversation
alexluong
force-pushed
the
feat/redis-pool-size
branch
from
August 31, 2026 22:04
d756b19 to
93f4af1
Compare
alexluong
force-pushed
the
feat/redis-pool-size
branch
from
September 1, 2026 07:58
93f4af1 to
bbde364
Compare
alexluong
marked this pull request as ready for review
September 1, 2026 07:58
alexbouchardd
approved these changes
Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
REDIS_POOL_SIZE(redis.pool_sizein YAML) to configure the go-redis connection pool size per client. Unset or0keeps go-redis's default of 10 × GOMAXPROCS, so existing deployments are unaffected. In cluster mode the value applies per node.The GOMAXPROCS-derived default cuts both ways: containers with small CPU limits get small pools that become a throughput ceiling when Redis round-trip latency is non-trivial, while large hosts hold hundreds of mostly idle connections per client. This exposes the standard knob to size the pool explicitly.