Óhoz
Em 14 de Nov de 2013 12:37, "Timothy W. Cook" escreveu:
> Well, this isn't likely a Django specific question but since this
> project is built in Django, I'd like to know how best to handle this
> issue.
>
> I have a view that calls a function and performs a long running
>
Celery might overkill they are other more simple solutions that only
involve your current database and cron jobs.
Regards,
Amirouche
2013/11/14 Jonathan Baker
> You're welcome. I just set celery+rabbitmq up on a new project, and while
> it can seem like a lot
You're welcome. I just set celery+rabbitmq up on a new project, and while
it can seem like a lot of steps (and potential information overload), it
isn't so bad once you get a grasp on the concepts.
One thing that recently bit me: once in production with running workers, if
the models your task
On Thu, Nov 14, 2013 at 9:37 AM, Timothy W. Cook wrote:
> Well, this isn't likely a Django specific question but since this
> project is built in Django, I'd like to know how best to handle this
> issue.
>
> I have a view that calls a function and performs a long running
>
Thanks Jonathan. Looks interesting from the FAQ.
I'll give it a shot and see what happens.
On Thu, Nov 14, 2013 at 12:39 PM, Jonathan Baker
wrote:
> This sounds like a good candidate for an async Celery task:
> http://docs.celeryproject.org/en/latest/index.html
>
>
This sounds like a good candidate for an async Celery task:
http://docs.celeryproject.org/en/latest/index.html
On Thu, Nov 14, 2013 at 7:37 AM, Timothy W. Cook wrote:
> Well, this isn't likely a Django specific question but since this
> project is built in Django, I'd like to
Well, this isn't likely a Django specific question but since this
project is built in Django, I'd like to know how best to handle this
issue.
I have a view that calls a function and performs a long running
process. It reads and processes a file, creating potentially
thousands of objects and can
7 matches
Mail list logo