Thanks Jeff,
I used celery backended by redis, not rabbitmq.
celery was used like:
@init_decorator
def view:
and in this decorator:
def init_decorator(*args, **kwargs):
celery_task.delay()
On Mon, Nov 12, 2012 at 11:23 PM, Jeff Van Voorst
<[email protected]>wrote:
> 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<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
