Setting the file. One moment.
Subchapter 7.25
references/support-topics/cold-start-initialization-bundle.mdMarkdown1 KBView on GitHub
Cold-start candidates need a code-path check, not only a project-setting check. First prove whether cold requests are paying for imports, module-scope setup, runtime choice, or dependency weight.
Use startTypeSplit, coldVsWarmLatencyP95, and coldByDeployment. In source, inspect module-scope SDK setup, database/client construction, top-level network calls, heavy dependencies, runtime exports, and deployment-local changes.
Do not blame cold starts when warm requests are similarly slow. Do not recommend keep-warm traffic or more memory before proving initialization or runtime pressure.
Name the cold-start share, cold-vs-warm gap, and exact initialization, dependency, or runtime line that explains it.