We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1G app = 4 CPU cores (cf ssh api -i 0 to log into one app instance, cat /proc/cpuinfo to see cores) https://docs.gunicorn.org/en/stable/run.html#commonly-used-arguments
cf ssh api -i 0
cat /proc/cpuinfo
Recommended workers is 2xCPUs+1 = 9 workers (currently 4 workers)
Completion criteria
dev
gunicorn --access-logfile - --error-logfile - --log-level info --timeout 300 -k gevent -w 9 webservices.rest:app
-w 9
-- Check the number of workers with ssh api and ps aux | grep gunicorn | grep -v grep | wc -l (subtract one) per https://stackoverflow.com/a/33107962
ssh api
ps aux | grep gunicorn | grep -v grep | wc -l
I couldn't get gunicorn to recognize the WEB_CONCURRENCY or GUNICORN_CMD_ARGS env vars.
WEB_CONCURRENCY
GUNICORN_CMD_ARGS
The text was updated successfully, but these errors were encountered:
lbeaufort
Successfully merging a pull request may close this issue.
1G app = 4 CPU cores
(
cf ssh api -i 0
to log into one app instance,cat /proc/cpuinfo
to see cores)https://docs.gunicorn.org/en/stable/run.html#commonly-used-arguments
Recommended workers is 2xCPUs+1 = 9 workers (currently 4 workers)
Completion criteria
dev
at 10 instances, note database CPU and connections start/endgunicorn --access-logfile - --error-logfile - --log-level info --timeout 300 -k gevent -w 9 webservices.rest:app
to-w 9
dev
, note database and connections CPU start/end-- Check the number of workers with
ssh api
andps aux | grep gunicorn | grep -v grep | wc -l
(subtract one) per https://stackoverflow.com/a/33107962I couldn't get gunicorn to recognize the
WEB_CONCURRENCY
orGUNICORN_CMD_ARGS
env vars.The text was updated successfully, but these errors were encountered: