On Oct 21, 6:44 pm, Javier Guerra <jav...@guerrag.com> wrote:
> On Wed, Oct 21, 2009 at 9:49 AM, Michael Thon <mike.t...@gmail.com> wrote:
> > Thanks for pointing me towards celery. Its probably overkill for what
> > I want to do right now but I'm going to try to set it up anyway.
>
> the roll-your-own alternative is just setting a DB table with the
> queued tasks, and a cron job (or a long-running daemon) that fetches
> the next job from the table to work on it. it's called 'Ghetto
> queues'. it works and for small setups can be much ligther, but for
> complex, or high-speed, or critical availability, it can quickly
> become a nightmare to set up right.
That's what I was thinking of doing after reading Jani's reply. I
could put the data crunching code into a view and then just set a cron
to fetch the view every couple of minutes. The jobs could overlap so
I'd have to make sure I don't have too many running concurrently
somehow.
I got celery and RabbitMQ installed without any trouble so if I have
time today I'll tinker with getting jobs running on it. I don't know
if celery will let me call other functions or shell commands outside
of the task function, or if the task function needs to be 'self
contained'. If not, then ghetto queue it is...
Mike
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
