-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Support Min connection pool parameter #3009
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I experienced the same problem. each initial set of connections takes more than 200 ms, so the api response time becomes > 1s |
@brianc we are working with I took a brief look at the code and it seems like it should be possible as an addition to pool logic. Would offer to contribute as well 🙌 |
I took a crack at addressing this. Would love to get your thoughts @brianc @charmander. |
Hey @brianc @charmander ,
Problem Statement: I have an application which is currently using the default configuration of node-postgres pool to connect to postgres. I have noticed that whenever we query the application - node-postgres connection pool always creates a new connection and so the total time taken for query execution is always between 3-5sec. If we re-use an idle connection for query execution - it just takes 2 millisecond to 300 millisecond.
Proposed Solution: I am thinking of keeping some idle connections in the pool - so that they could be used whenever the database is queried. Something like this -
I am open to submitting a PR for the above feature but thought of first discussing it with the community whether this would be a feature worth exploring.
The text was updated successfully, but these errors were encountered: