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
Unify app server: Gunicorn or uWSGI or other? #431
Comments
Maybe re-evaluate the choice, as the article I referenced is old! These posts show different results:
Regardless, we should unify to one app server, and pay attention to performance, as they are not all alike! |
We have decided to stick with Gunicorn for the main web app for now, but will revisit in the future. |
I think my links above are outdated (i.e. Meinheld hasn't seen any dev for 18 months) because the industry move to full ASGI servers about 2 years ago. See: It seems like Uvicorn is fastest, and although it supports HTTP/1.1 and WebSockets, it does not (yet) support HTTP/2. An alternate is Daphne, developed by the Django team, built with pure python, and supports HTTP, HTTP2 and WebSocket protocols. @ptomasula, lets explore which of these can be installed on ARM64 architectures (i.e. AWS Graviton). |
WOFpy uses uWSGI application server framework, and it looks to be much faster than Gunicorn. See https://blog.kgriffs.com/2012/12/18/uwsgi-vs-gunicorn-vs-node-benchmarks.html
Since we'll want to unify the stack, let's consider switching to uWSGI.
https://uwsgi-docs.readthedocs.io
The text was updated successfully, but these errors were encountered: