What can I do in my own code to reduce cold starts?
Keep the deployment package small, import only what you use, do heavy initialisation lazily or outside the critical path, choose a fast-starting runtime when latency matters, reuse connections created outside the handler, and avoid loading large models or files at startup unless a snapshot or provisioned capacity covers it.
Answered in
Serverless Cold Starts Explained: MicroVMs, Snapshots and What You Can ControlWhy a function's first call is slow, how microVMs and snapshot restore cut it, and the code and config choices that shrink cold starts on your side.
Read the full analysisOther questions this article answers
More web performance questions
- What problem does HTTP/2 solve compared with HTTP/1.1?
- What is head-of-line blocking and does HTTP/2 remove it?
- Why does HTTP/3 use UDP?
- How can I check which HTTP version a site is using?
- What is the difference between latency, bandwidth and throughput?
- Why measure p95 and p99 instead of the average?
- What is the quickest win for network latency?
- How do I decide whether to make something asynchronous?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Web Performance beat.