Skip to content
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

What is the behaviour when set workers and threads using wSGI? #63

Open
daviddelucca opened this issue Jul 15, 2024 · 1 comment
Open

Comments

@daviddelucca
Copy link

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:

--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?

@daviddelucca 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
@altairbow
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants