I used celery, but I think you didn't mean that. I used processes, not threads. I didn't use the other async mode either.
On Mon, Nov 12, 2012 at 11:10 PM, Roberto De Ioris <[email protected]> wrote: > > Il giorno 12/nov/2012, alle ore 15:55, Samuel <[email protected]> ha > scritto: > > > Hi, > > > > I recently found a lot of nginx timeouts errors, but after checking > uwsgitop, I found a lot of workers are idling, the average time per request > is around 10-40 ms, and I set uwsgi_read_timeout as 30s (not 30ms) > > > > uwsgitop said workers are idle, so uwsgi was not handling a lot of > requests, so why nginx showed a lot of timeouts? > > > > When nginx timeout starts, my site is very slow; when it doesn't appear, > the site can be very fast. > > > > so why the site is busy, but the uwsgi worker can be idle? I expect > everyone working hard when busy. > > > > > > -- > > samuel > > > > > > Are you using threads or some kind of async mode ? > > In that scenario the status monitoring is a bit flaky (uWSGI already fixed > that, but uwsgitop needs to be updated) > > -- > Roberto De Ioris > http://unbit.it > JID: [email protected] > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- *吴焱红(Samuel)* 博客: blog.shanbay.com
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
