Hi. No, at least not at the production site, because memory consumption (we still have memory leaks) and application initialization is too high and each process gets > 450 MB after about 1000 requests (aprox. 30-60 min). The VM has 4GB RAM. Now I have 4 workers.
Currently, I'm not able to reproduce the error reliably. Regards. Ernesto Revilla Área Técnica TangramBPM.es Tlf: 630 244 136 2017-09-28 7:41 GMT+02:00 Avraham Serour <[email protected]>: > did you try running it without threads? > > On Wed, Sep 27, 2017 at 5:26 PM, Ernesto Revilla <[email protected]> > wrote: > >> Dear all. >> >> Could anyone please lend me a hand? >> >> From time to time, the respawned (--reload-on-rss=450) process is blocked >> and does not accept any connections. I get a "Connection timed out" error >> in Nginx. >> >> https://github.com/unbit/uwsgi/issues/1599 >> >> I did already strace it and find the process and all its threads waiting >> on futex. >> >> I haven't read the "reload code", but it's like if the forked process >> inherits some other futex (we can see it with strace). >> >> I've been able to reproduce the behaviour using Apache Bench (ab) on a >> test server. I was not able to reproduce it on Ubuntu 16.04. >> >> Thanks in advance. >> Best regards. >> >> >> >> Ernesto Revilla >> Área Técnica >> TangramBPM.es >> Tlf: 630 244 136 >> >> >> >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> >> > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
