-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
switch waitress for gunicorn #98
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comment. LGTM.
By the way, that's a very clear PR describing the changes. I would suggest you copy/paste this description into the merge commit description to preserve it and make it available even if github is not available (ex: no network). |
@fmigneault I think you can remove |
@fmigneault Thanks for the PR :) Feel free to merge. |
Fixes #97 Replaces `waitress` by `gunicorn` by default. `waitress` seems to do some kind of deduplication of contents with extra read/write of chucks during data streaming. Could not find any way to avoid `waitress` to do this with some option/flag. Tests results can be found here: - #97 (comment) - #97 (comment) Leaving waitress in dependencies so that pre-existing deploys can use whichever they want between `gunicorn` / `waitress`. Important note: `gunicorn > 20` needs to be started with `pserve` to have correct port assigned. There is a change of parsing `PasteDeploy` config where starting directly with `gunicorn` doesn't detect the right port. (doesn't matter that much in this case, since default is 8000 which is also the one employed) Regarless, Docker image was already using `pserve`, so everything should work just fine.
bump twitcher v0.5.4 (performance fix bird-house/twitcher#98)
Fixes #97
Replaces
waitress
bygunicorn
by default.waitress
seems to do some kind of deduplication of contents with extra read/write of chucks during data streaming.I could not find any way to avoid
waitress
to do this with some option/flag.Tests results can be found here:
#97 (comment)
#97 (comment)
I leave
waitress
in dependencies so that pre-existing deploys can use whichever they want betweengunicorn
/waitress
.(if this is not an issue, we can remove it also)
Important note:
gunicorn > 20
needs to be started withpserve
to have correct port assigned.There is a change of parsing PasteDeploy config where starting directly with
gunicorn
doesn't detect the right port.(doesn't matter that much in this case, since default is
8000
which is also the one employed)Regarless, Docker image was already using
pserve
, so everything should work just fine.