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
- Error: Timed out waiting for runtime
I am trying to call a function on appwrite cloud (python 3.9), but I keep getting the above error (Timed out waiting for runtime) saying it timed out after 30 s...
- Random function timeouts
Sometimes my function runs without issue and I can see my logs in the Logs tab on cloud.appwrite.io. Other times, the function fails with a 500 status code, the...
- I am not getting "to" when email receive...
I am using cloud function to send an email when email received it doesn't have "to" email address. Please see attached image. My cloud function detail: built w...