Replies: 1 comment
-
|
Your FastAPI app took more than 10 seconds to start. Lambda restarted the runtime at 9930 ms and re-initialize the runtime. 1762529085657,"INIT_REPORT Init Duration: 9930.03 ms Phase: init Status: timeout"The app took more than 18 seconds to answer http requests. 1762529103721,"INFO lambda_web_adapter: app is not ready after 18000ms url=http://127.0.0.1:8080/health"You can reduce the dependencies imported during the startup, or use Lambda SnapStart. Lambda SnapStart might be easier option to reduce the cold start time. Checkout the Lambda Developer Guide and the launch blog post. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We have a FastAPI app running under uvicorn that's very slow to start-up, causing the Lambda to even hit its 29s timeout. Is it possible from the logs below to tell which part is slow?
Beta Was this translation helpful? Give feedback.
All reactions