Replies: 1 comment 3 replies
-
There is no need to "look on the internet". This package has official documentation that shows how to run both Gunicorn and uWSGI. For both, you should use a single worker. Gunicorn: https://flask-socketio.readthedocs.io/en/latest/deployment.html#gunicorn-web-server If you want to run multiple workers, then run multiple Gunicorns or uWSGIs, with nginx as a load balancer in front. Nginx docs: https://flask-socketio.readthedocs.io/en/latest/deployment.html#using-nginx-as-a-websocket-reverse-proxy |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I saw other people's information on the Internet that they can only use
uWSGI
to perform multiple jobs, but not gunicorn. I want to know which one should be used to perform multiplework
.I useing socketIO(messages_queue='redis')
I tested gunicorn work=10, but some connections have been timed out during the test, I don't know why, if I change to work=1, then it will be connected quickly.
when i connect
clinet
if setting
work=1
, it is work .Beta Was this translation helpful? Give feedback.
All reactions