Re: [modwsgi] Server-Sent Events (SEE) blocking all threads

2019-08-06 Thread Graham Dumpleton
> On 6 Aug 2019, at 21:03, Orestis Zambounis > wrote: > > Many thanks. I'm going to dive into gunicorn, gevents etc. > As I am deploying to Elastic beanstalk which is set up with Apache/mod_wsgi > by default would you recommend to look into switching the server to gunicorn > or use some

Re: [modwsgi] Server-Sent Events (SEE) blocking all threads

2019-08-06 Thread Orestis Zambounis
Many thanks. I'm going to dive into gunicorn, gevents etc. As I am deploying to Elastic beanstalk which is set up with Apache/mod_wsgi by default would you recommend to look into switching the server to gunicorn or use some other strategy for real-time communication such as sockets in terms of

Re: [modwsgi] Server-Sent Events (SEE) blocking all threads

2019-08-05 Thread Graham Dumpleton
The only WSGI servers where this would work is those which are implemented using greenlets. Thus, eventlet and gevent modes of gunicorn. Any WSGI server which uses normal processes/threads, SSE will not really work well because of restrictions on size of workers available. > On 5 Aug 2019, at

[modwsgi] Server-Sent Events (SEE) blocking all threads

2019-08-05 Thread Orestis Zambounis
My flask application implements SSE to push updates to each of my users. I.e. each of my users gets individual updates and therefore unique SSE connections. I deploy the application to mod_wsgi. Now mod_wsgi allows me to use a fixed number of threads (default 15) which are quickly all blocked