Connection pool docs #2845
Labels
Comments
rickyssj2
added a commit
to rickyssj2/node-redis
that referenced
this issue
Feb 18, 2025
…in isolationPoolOptions - Added a Connection Pooling section in `createClient` documentation to clarify that a single connection is typically sufficient and to provide guidance on when to use a connection pool. - Updated `isolationPoolOptions` description with a more precise explanation and replaced the broken link with a reference to `createClientPool`. - Changes made based on issue redis#2845.
|
I have updated the docs. Let me know if anything else is needed. Thanks :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
It would be great to explain (for example in client-configuration.md that single connection is sufficient most of the time and therefore there is no need for connection pooling.
I was looking in docs for options regarding connection pools (as I usually do when I set up the database client) and i found none (except for isolated connection pool). As I looked briefly it seems that commands are sent to the server as fast as the underlying socket allows it
The text was updated successfully, but these errors were encountered: