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

Investigate updating gunicorn worker counts #10429

Open
jimchamp opened this issue Feb 6, 2025 · 0 comments
Open

Investigate updating gunicorn worker counts #10429

jimchamp opened this issue Feb 6, 2025 · 0 comments
Labels
Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Lead Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]

Comments

@jimchamp
Copy link
Collaborator

jimchamp commented Feb 6, 2025

Proposal

@cdrini points out that many of our gunicorn workers are sitting idle waiting for requests. As per gunicorn's guidance, we may be using too many workers.

Let's investigate lower the number of gunicorn workers in our servers.

Justification

Having too many idle workers can negatively affect site performance.

Adding more statsD instrumentation could help us determine if we should adjust the worker count, and by how much.

Breakdown

Requirements Checklist

  • [ ]

Related files

Stakeholders


Instructions for Contributors

Please run these commands to ensure your repository is up to date before creating a new branch to work on this issue and each time after pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.

@jimchamp jimchamp added Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Lead Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed] labels Feb 6, 2025
@mekarpeles mekarpeles added this to the Sprint 2025-02 milestone Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Lead Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]
Projects
None yet
Development

No branches or pull requests

2 participants