I'm looking for a way to scale appwrite running selfhosted in docker swarm. According to the benchmark guide https://book.appread.io/benchmarks#docker-swarm appwrite running in docker swarm can have only one executor and appwrite-worker-functions container and they both have to run on the same node. Which makes functions basically only scale vertically when running in docker swarm.
I have gotten suggestions that modifying the OCR image might help with this: From @Binyamin "There's a small challenge you'll need to overcome when deploying Appwrite into Docker Swarm as Appwrite uses OpenSwoole in-ram table for managing the running functions containers ... That said 1000-2000 rps mean 3,600,000 - 7,200,000 and Appwrite should be able to handle pretty nice, but you'll need to either overcome and modify the ORC image or go with Horizontal scaling."
I think he means instead of swarm, just setting independent appwrite instances and set a load balancer to distribute the traffic between the instances, but not sure
Recommended threads
- I'm getting an error on the console "j?....
On my self hosted instance version 1.8.1 the console is giving me this error when trying to view the rows for a table I recently created. My application is read...
- local build `composer installer:dev` iss...
setup - dev container (default linux universal) WSL (test with gh codespace too) - php 8.5.7 - all extensions installed - `composer install` fine - `composer...
- Function global variables
when i create a top-level global variable in go or bun how will it behave? is the heap getting renewed on every execution or could i do some kind of temp. cachi...