Rank 2: Process
What determines the function execution duration?
Appwrite 1.4.2 is a self-hosted
Runtime: Dart (dart-3.0)
The first execution is 2-3 seconds. Two series of 3 executions.
Is the problem in bad hardware, or should it be?
Votes
0
Replies
17
Participants
Unknown
Messages
18
Rank 2: Process
What determines the function execution duration?
Appwrite 1.4.2 is a self-hosted
Runtime: Dart (dart-3.0)
The first execution is 2-3 seconds. Two series of 3 executions.
Is the problem in bad hardware, or should it be?
What is your function threshold timeout?
The first one should take a bit more as it starting up the server.
Rank 2: Process
function threshold timeout - default 15 sec.
Than if it was on the exact hour time, then it might be shut down
Can you check the results of
docker ps -a
To see how long the function container is running?
Rank 2: Process
"worker-functions" 26 hours ago Up 26 hours 80/tcp
It should be something with the function ID as is name
You mean timeout or threshold?
You set the threshold in the .env file
Rank 2: Process
60
So that's is 60 seconds
Meaning if your function is inactive for 60 seconds it will get shut down and will have a cold boot (which is 2-3 seconds) in your case before starting.
Change that number to 3600 for example to make it shut down any inactive function after one hour.
Remember to reload your docker
docker compose down && docker compose up -d
And let us know if you still experience the long 2-3 seconds execution time.
Rank 2: Process
Yes
That make sense
As you can see is brand new (just 8 seconds) and that is because it was shut down after 15 seconds of being inactive
Rank 2: Process
thank you i understand can be closed👍
btw, there's a bug that will be fixed in 1.4.3 where the runtime containers were being removed way too soon. see https://github.com/appwrite/appwrite/pull/6235
Rank 2: Process
In my case, changing the threshold timeout helped.
[SOLVED] Function execution duration