Skip to content
This repository

Increase number of gunicorn workers to 4 #44

Merged
merged 1 commit into from about 1 year ago

2 participants

Rob Young James Abley
Rob Young
Owner

No description provided.

James Abley
Owner

Any particular reason why 4 was chosen?

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

Rob Young
Owner

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?

Rob Young robyoung merged commit dfb0962 into from April 10, 2013
Rob Young robyoung closed this April 10, 2013
Rob Young robyoung deleted the branch April 10, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Showing 1 unique commit by 1 author.

Apr 09, 2013
Rob Young Increase number of gunicorn workers to 4 aa0bb7b
This page is out of date. Refresh to see the latest.
2  Procfile-read
... ...
@@ -1 +1 @@
1  
-web: venv/bin/gunicorn -blocalhost:3038 backdrop.read.api:app
  1
+web: venv/bin/gunicorn -blocalhost:3038 --workers=4 backdrop.read.api:app
2  Procfile-write
... ...
@@ -1 +1 @@
1  
-web: venv/bin/gunicorn -blocalhost:3039 backdrop.write.api:app
  1
+web: venv/bin/gunicorn -blocalhost:3039 --workers=4 backdrop.write.api:app
Commit_comment_tip

Tip: You can add notes to lines in a file. Hover to the left of a line to make a note

Something went wrong with that request. Please try again.