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
This is an awesome library that I'm testing to implement into our production environment to solve a lot of connections being open by Django.
For now, it's working smooth and docs are pretty clear, I just have a question about what is the behavior when my gunicorn has the following parameters:
--workers=3
--threads=4
If I had only workers set, the maximum number of connections will not exceed workers * pool_size + workers * max_pool. But what's happen when set threads?
The text was updated successfully, but these errors were encountered:
daviddelucca
changed the title
What is the behavious when set workers and threads using wSGI?
What is the behaviour when set workers and threads using wSGI?
Jul 15, 2024
The maximum number of connection pools is limited to a single connection pool. Each process will have a separate connection pool. If there is only one process, the total number of database connections will not exceed the maximum limit of the connection pool.
Hey there!
This is an awesome library that I'm testing to implement into our production environment to solve a lot of connections being open by Django.
For now, it's working smooth and docs are pretty clear, I just have a question about what is the behavior when my gunicorn has the following parameters:
If I had only workers set, the maximum number of connections will not exceed workers * pool_size + workers * max_pool. But what's happen when set threads?
The text was updated successfully, but these errors were encountered: