On 26/10/2010 10:30, SplitIce wrote:
> Ok although I dont know the scale of your site that formulae always
> works, A decent response time for an application is 0.05s, even most
> forums will return 0.2s so if you are getting values higher than that
> then your problem is in your script.
>> This isnt really a nginx problem, its more PHP related.
>> On Tue, Oct 26, 2010 at 8:24 PM, Xin Liu <liuxin84 at gmail.com> <mailto:liuxin84 at gmail.com>> wrote:
>> It's getting worse and worse.
> From php-fpm.log, there is no error.
> But from nginx error.log, there are lots of errors
>>> [error] 21819#0: *16895 connect() to unix:/tmp/php-cgi.sock
> failed (11: Resource temporarily unavailable) while connecting to
> upstream, client: 119.145.137.49, server: localhost,......
>>I think this means that nginx has tried to pass a request to php, but
php is unable to accept it due to having too much work to do. It can't
make any more workers, and so it has to wait for a worker to finish
before it can accept the request.
Most probable is that the most recent change to the php script has
caused some form of looping or a very inefficient lookup in the database
(Has in index been removed recently?)
Try going back to the php code and database before the last change, and
seeing if that improves things.
Regards
Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20101026/6c4923d3/attachment.html>