fix: reduce gunicorn concurrency to at most 4 * maximum available cor… - #259
Merged
Merged
Conversation
garethgeorge
force-pushed
the
garethgeorge/concurrency
branch
4 times, most recently
from
July 10, 2023 22:13
9590b26 to
fe5c261
Compare
garethgeorge
force-pushed
the
garethgeorge/concurrency
branch
from
July 10, 2023 22:16
fe5c261 to
56480bb
Compare
KaylaNguyen
approved these changes
Jul 10, 2023
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updates gunicorn's multithreading logic to derive the maximum concurrency the container can handle from the number of cores available to the functon. 4 invocations per core (given that memory additionally scales with cores) will be a good default concurrency limit that most functions will support without running into resource problems.