
Hello, I want to test some stuff and I'm not pretty sure on how executor and worker-functions work.
So I'm asking for a bit of help understanding these two containers, and looking for a tutorial on how to scale them.
My main purpose: Executing functions faster, and understand how these containers works.



Thank you so much Steven. I'm looking into it.
But, IDK if it's makes sense, as I said, I'm testing stuff. If I want to create another node in the same machine that helps executing functions to make it faster, it could be possible?
If its so, how I can do that?

That would help with async executions, sure

The easiest thing to do is to put more worker containers in a docker-compose.override.yml file

Hello again Steven, please, can you share a bit on how to do that? I just want to be sure to no mess up something.
I want to test as well, something of an old post from myself where I was asking to reduce times on "events" delay when executing functions.

Like this but using the latest docker compose and putting it in a docker-compose.override.yml file: https://github.com/appwrite/appwrite/issues/1425#issuecomment-886221620

Thank you so much Steven!

@Ponguta_ this video may be helpful https://www.youtube.com/watch?v=Msv9TpE4C3w

I will check it out, thank you!

That doesn't explain how to run them parallel...

ok, i just thought this can be helpful.

No worries
Recommended threads
- Having errors migrating to cloud
Project will not migrate compeltely
- ENV vars not updating
When i do `nano .env` it shows `_APP_DOMAIN_TARGET=` as set to my domain, but when i do `docker compose exec appwrite vars` it shows `_APP_DOMAIN_TARGET=` as ...
- Index with the requested key already exi...
I'm using appwrite cli to create DB and I'm getting index_already_exists Is there a way to undestand the index name and maybe to skip if it's already exits?
