Increase number of gunicorn workers to 4 #44

Merged
merged 1 commit into from Apr 10, 2013

2 participants

@robyoung

No description provided.

@jabley

Any particular reason why 4 was chosen?

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

@robyoung

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 Apr 10, 2013

1 check passed

Details default Build #161 succeeded on Jenkins
@robyoung robyoung deleted the increase-gunicorn-workers branch Apr 10, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment