DjangoBot: #celery

asksol: amqp as a tombstone backend, that warning, i wanted to confirm what "receive the result once" means :)

i set the concurrency to 4, and it shows 5 procs, kinda of odd ;)

yay, celery running on demo site :D

ooo, error emails :D

and i suppose i should fork/commit this back, but for now ill just post here: http://celeryproject.org/reference/celery.task....

kwargs/args should really be optional I think

in fact i will probably fork tomorrow

i think i have some useful additions to commit back

davidcramer: there's no easy way to see queued tasks until celerymon is done

5 processes, one main process and 4 pool workers?

you can see what they do in ps listings if you install the "setproctitle" module

thanks!

amqp backend means you send the result as a message, so you can only consume that result once

so if you do result.get() in two different processes, you will have a deadlock

or deadlock is probably not the right term

plan for 1.2 is to have an option to cache the result in a result backend

so send back result with amqp, e.g. store it in redis when consumed

I'm loving Celery :D

we've gotten it all moved into tasks and its working amazing

so any heavy task no longer happens on the web

should make scaling a lot easier as well

I'm assuming I could just have a project+celery install on any server, then one rabbitmq install for it to communicate with? Easy scaling, ya?

:)

indeed

cool

I did have one transactional issue

and I have had the same issue without celery, so I would say its more of a flaw in Django

for some reason django doesnt commit the save() transaction here

(at the bottom)