Gunicorn vs uWSGI #2008
rajan-code
started this conversation in
General
Replies: 1 comment
-
@rajan-code first of all, for 100 connections a single worker is very likely more than enough. I personally choose gunicorn over uwsgi. Launching several single worker processes means exactly that. You run |
Beta Was this translation helpful? Give feedback.
0 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.
-
If I understand the documentation correctly, if nginx is configured correctly and a message queue is used, both gunicorn and uwsgi support multiple workers right?
Let's say I have no more than 100 websocket concurrent connections. Does uwsgi have any advantages that would make it worth using?
Also, the docs say
The workaround to use multiple worker processes with gunicorn is to launch several single-worker instances
does this mean simply set number of workers to a num greater than 1 e.g.
gunicorn -w 2 --threads 100 module:app
?Beta Was this translation helpful? Give feedback.
All reactions