massadmin + django-denorm leads to performance problems... make them async? about django-mass-edit HOT 2 CLOSED

Async is a bit scary because an error would not notify the end user. I'd be open to a settings.py option that is disabled by default. We also can't have a queuing system as a required dependency.

"Turn off denormalizations for a bit during massadmin" I'm not familiar with the project so I can't really comment here.

Unrelated do you like django-rq? I'm a bit annoyed with Celery but it seems the go to option.

from django-mass-edit.

Yea, I agree with you. This really should be the responsibility of the denorm library, or else the responsibility of my code to override the behavior. It is complex and quirky enough I'll probably go with a lightweight clone or rewrite though, which is a bummer.

As for django-rq, yes I like it. Very lightweight and painless. I'm not sure what its scaling limitations are. Surely there must be a point at which a dedicated broker like RabbitMQ is superior to Redis. It has been a while since I used Celery, and I have only used it as a "client" - it was someone else's job to keep the whole thing running smoohtly - so I can't say how much simpler django-rq might be. If you are already using redis as the backing store for celery, then it will be very painless to try it out.

from django-mass-edit.