Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Increase number of gunicorn workers to 4 #44

merged 1 commit into from

2 participants


No description provided.


Any particular reason why 4 was chosen?

Presumably we're expecting more reads than writes, so should they be the same size?


No, this is in reaction to discovering that, by default, gunicorn starts up with just one worker. At the moment the write api is going to be incredibly low traffic, it does also have a higher impact to not being available. The read api will not have a massive amount of traffic but there are multiple requests per page so more concurrency would be useful.
What about 2 for the write api and 4 for the read api?

@robyoung robyoung merged commit dfb0962 into master

1 check passed

Details default Build #161 succeeded on Jenkins
@robyoung robyoung deleted the increase-gunicorn-workers branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Apr 9, 2013
  1. @robyoung
This page is out of date. Refresh to see the latest.
Showing with 2 additions and 2 deletions.
  1. +1 −1  Procfile-read
  2. +1 −1  Procfile-write
2  Procfile-read
@@ -1 +1 @@
-web: venv/bin/gunicorn -blocalhost:3038
+web: venv/bin/gunicorn -blocalhost:3038 --workers=4
2  Procfile-write
@@ -1 +1 @@
-web: venv/bin/gunicorn -blocalhost:3039 backdrop.write.api:app
+web: venv/bin/gunicorn -blocalhost:3039 --workers=4 backdrop.write.api:app
Something went wrong with that request. Please try again.