I don't know if this helps, but when I used celery I had to choose an
underlying implementation for queues and messaging. Can you monitor the
celery queue? It might be overrun, be a bottleneck, etc.
Also, it would be helpful to know where you are using celery in the
nginx + uwsgi stack. There is some documentation about ampq with uwsgi,
you could also look there if you are using celery in a similar manner
(maybe via RabbitMQ).
--Jeff
On 11/12/12 9:18 AM, Samuel wrote:
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.
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
