Do you have enough workers to handle 200 concurrent requests? Requests are queuing in backlog waiting for your app to process them (default backlog is 100 requests), once the queue is full you will get connect() error.
2013/9/25 Darko Luketic <[email protected]> > Hello, > > I was doing a simple ab -n10000 -c200 test > with various php projects locally. > > And the results across all tests were ~9800 non 2xx responses. > Now I've read the error log and it said: > connect() to unix:/tmp/uwsgi-php.sock failed (11: Resource temporarily > unavailable) while connecting to upstream > Now I've googled and apparently that errormessage says that the socket is > blocking and the connection was blocked because of too many processes > trying to query it. > > My question is, how do I increase this limitation? > > cat /proc/sys/fs/file-max > 3249525 > > ipcs -l > > ------ Messages Limits -------- > max queues system wide = 32768 > max size of message (bytes) = 8192 > default max size of queue (bytes) = 16384 > > ------ Shared Memory Limits -------- > max number of segments = 4096 > max seg size (kbytes) = 32768 > max total shared memory (kbytes) = 8388608 > min seg size (bytes) = 1 > > ------ Semaphore Limits -------- > max number of arrays = 128 > max semaphores per array = 250 > max semaphores system wide = 32000 > max ops per semop call = 32 > semaphore max value = 32767 > > ______________________________**_________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/**mailman/listinfo/uwsgi<http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi> > -- Łukasz Mierzwa
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
