Hey guys, for long running tasks, like processing a large database dump or using some browser automation, is locking a worker on it the only way to do so? Given the limited amount of workers we can spin.
TL;DR
Question: Is locking a worker the only way to handle long running tasks, considering the limited number of available workers?
Solution: One possible solution to handle long running tasks without locking a worker is to use task queuing and scheduling systems like Celery. This allows you to distribute the tasks across multiple workers and prioritize them based on their importance and resource requirements. This way, you can handle long running tasks efficiently without blocking available workers.Recommended threads
- After assigning a domain to my Dart func...
I’ve attached the images. Could anyone please explain how this execution is being performed?
- I can't UNPAUSE my project with the free...
I received an email notifying me that my project had been paused due to inactivity, and the email included a link to "Restore project." However, that button red...
- Error trying to deploy functions from CL...
✗ Error • on-auth-create (6a00b2ab000c9ce2949b) • Server Error ✗ Error: No functions were pushed. Prject ID: 69ffe0270033a4ac420a