|
|
|
|
|
by Schweigi
2084 days ago
|
|
I can definitely confirm the issues. We had memory issues, stuck tasks and lost tasks (despite late ACK). It really requires a lot of fine tuning to get right. We started switching to AWS SQS four years ago and created a thin Django/Python wrapper [0] for it. Now we handle tasks in the hundred of millions a day and I don't want to think about how that would have turned out if we didn't switch. But honestly, people working on Celery in their free time (i think) so who am I to complain. I can see that monetary support would be necessary to make it better. But in my opinion the project just got too big and it will be difficult to fix all the underlying issues. [0]: https://github.com/cuda-networks/django-eb-sqs |
|