-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚀 Feature: Cloud functions keep alive #2994
Comments
Hey There 👋 |
@PineappleIOnic also i think i dont need it for all my functions, just for special functions that brings data to my front end.. with threshold paramter its active for all my containers.. and i also its not available in the appwrite console, which is also a bad user experience ;) |
I think we can consider having this be a console setting, per container. CC: @PineappleIOnic |
Is setting this per function now possible? Or is the docker environment variable still counting for all project functions? |
@s3ppo what runtime are you using that takes 5 second to cold start? |
Was in an older release now its about 200ms on a cold start versus 2ms on a warm start |
🔖 Feature description
Hi all,
and first of all i love the new functions and also their speed :)
i run into a small problem with the cold start of sync functions.
if a function wasnt used for a longer time, it shuts the container down and the next start needs up to 5 seconds to bring a result to the app (UI).
so i think it would be very cool to have a option in the settings of a function where i can define a keep alive checkbox. if i check this, the shutwdown of the container does not happen and it would bring me faster responses to my front end.
or maybe a setting where i can define for how long i want the container warmed up.. for not critically performance or background task i can define 1 minute, and for sync functions that brings responses to the front end, i can define 24h.
please let me know if this is possible? :)
🎤 Pitch
pls see description :)
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: