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.

Sign up for GitHub

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

Jump to bottom

Automatically configure WEB_CONCURRENCY #267

Open
edmorley opened this issue Sep 7, 2024 · 0 comments
Open

Automatically configure WEB_CONCURRENCY #267

edmorley opened this issue Sep 7, 2024 · 0 comments
Labels
classic buildpack parity Features required for parity with the classic Heroku Python buildpack semver: major

Comments

@edmorley
Copy link
Member

edmorley commented Sep 7, 2024 •
edited
Loading

The classic Python buildpack automatically configures the WEB_CONCURRENCY env var based on available total CPU and RAM:
https://github.com/heroku/heroku-buildpack-python/blob/main/vendor/WEB_CONCURRENCY.sh
https://devcenter.heroku.com/articles/python-concurrency

The env var is then used by web servers like gunicorn and uvicorn to automatically set the number of worker processes to spawn.

We should add something similar to the CNB.

GUS-W-9538302.
@edmorley edmorley added classic buildpack parity Features required for parity with the classic Heroku Python buildpack semver: major labels Sep 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
classic buildpack parity Features required for parity with the classic Heroku Python buildpack semver: major
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@edmorley