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
{{ message }}
This repository was archived by the owner on Feb 27, 2025. It is now read-only.
Since Redis itself is a serial protocol, we're limited to 1 command at a time, having a connection pool would solve this issue and drastically improve performance (Especially on multi-threaded redis like KeyDB).
I suggest a number by default to open multiple connections to the same port and an array of connections for custom hosts and ports (ex. for clusters).
The text was updated successfully, but these errors were encountered:
By default, I'd rather keep things as simple as possible. I'd be surprised if the current approach would ever be the source of a performance bottleneck and should be more than sufficient, in terms of performance, for most use cases. Either way, I'd happily look at a PR exploring this functionality.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since Redis itself is a serial protocol, we're limited to 1 command at a time, having a connection pool would solve this issue and drastically improve performance (Especially on multi-threaded redis like KeyDB).
I suggest a number by default to open multiple connections to the same port and an array of connections for custom hosts and ports (ex. for clusters).
The text was updated successfully, but these errors were encountered: