You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all this is a great project! We absolutely love it and it extends the functionality of Lambda really nicely in a relatively simple way.
We are experiencing slow init times however when using this in our environment.
Lambda base image init: 250ms with some spikes up to 2000ms
Lambda base image with lambda-web-adapter starting FastAPI: 5111ms! (This is very consistent for a cold start)
The FastAPI code being started is their very basic hello world getting started example:
Hmm, I usually see high cold start times in the first a few cold starts after the function is created or updated. This is because of the cold cache in Lambda Service. However, the cold starts after that are much faster. See the test results here.
Could you deploy the FastAPI example and check the cold start time?
That is an awesome analysis in that other thread! Thank you so much for that. I apologize that didn't show up in my search. I think the discussion over there and your tips are enough. Thank you very much!
Hello,
First of all this is a great project! We absolutely love it and it extends the functionality of Lambda really nicely in a relatively simple way.
We are experiencing slow init times however when using this in our environment.
Lambda base image init: 250ms with some spikes up to 2000ms
Lambda base image with lambda-web-adapter starting FastAPI: 5111ms! (This is very consistent for a cold start)
The FastAPI code being started is their very basic hello world getting started example:
test_api/__init__.py
And it's started from the
Dockerfile
:The lambda logs don't seem to reflect the long startup init process:
Any tips on speeding this up?
Thanks a lot!
The text was updated successfully, but these errors were encountered: