Tune gunicorn lifecycle for streaming requests#101
Merged
wilsonccccc merged 1 commit intoMay 16, 2026
Conversation
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
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.
Summary
gunicorn_conf.pyso lifecycle parameters are explicit and env-overridable.max_requestsworker recycling by default to avoid interrupting streaming/v1/chat/completionsrequests.Context
Railway HTTP logs showed many
/v1/chat/completions502s with upstreamconnection closed unexpectedly. The old deployment also showed repeatedMaximum request limit ... Terminating processevents, which can recycle workers while streaming requests are active.Validation
python3 -m py_compile gunicorn_conf.pygunicorn_conf.pylocally and confirmed defaults:timeout=300,graceful_timeout=300,keepalive=75,max_requests=0,max_requests_jitter=0.git diff --check HEAD~1..HEAD