On Thu, Apr 26, 2018 at 6:35 PM, Roberto De Ioris <robe...@unbit.it> wrote:
> > > Hello, > > > > We see the following messages in logs: > > > > uWSGI listen queue of socket "0.0.0.0:5002" (fd: 10) full !!! (101/100) > > > > It's not related to restart. I can reproduce it by bombarding app using > ab > > tool: > > > > ab -k -l -r -c 200 -n 10000 http://192.168.1.48:5002/ > > > > > > HI, ab is not a good tool for this kind of tests, by the way, it looks > Why? it does the job of reproducing problem and simulating concurrent pressure. > like the system is not able to dequeue connections fast enough. > and I wonder why. I would increase the listen queue (remember that on linux you need to set > values in /proc files) > Increasing listen queue will just make the problem worse. > > -- > Roberto De Ioris > http://unbit.com > _______________________________________________ > uWSGI mailing list > uWSGI@lists.unbit.it > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Руслан Закиров Руководитель отдела разработки веб-сервисов +7(916) 597-92-69, ruz @ <http://www.sports.ru/>
_______________________________________________ uWSGI mailing list uWSGI@lists.unbit.it http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
