Set max-requests-jitter parameter to gunicorn #431
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jb3
added
area: backend
jerbob
approved these changes
Dec 5, 2020
SebastiaanZ
requested changes
Dec 6, 2020
ghost
added
s: waiting for author
Co-authored-by: Sebastiaan Zeeff <33516116+SebastiaanZ@users.noreply.github.com>
ghost
added
needs 1 approval
and removed
s: waiting for author
SebastiaanZ
approved these changes
Dec 6, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Set the max requests parameter for gunicorn to restart our workers between 1 and 1000 requests to help control the damage of memory leaks. This comes after we observed over 1GB RAM usage from our site container.
A bonus feature of this PR is that it integrates the statsd client inside gunicorn to report to our graphite server so we should be able to measure metric data.