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
- Function deployment failed: Unable to re...
Hi Appwrite team, I have been experiencing persistent errors when i attempt to push my appwrite functions. The logs on the deployment detail page on the console...
- My cloud functions failing 3 days ago (P...
Hi, My cloud function using python has been failing for 3 days, I didn't push any new deployments... Its something to do with it not recognising the entrypoi...
- Scheduled works locking the entire Maria...
I have a scheduled function and apparently that or something is locking the entire MariaDB database and Appwrite is giving MariaDB errors. This error persists e...