Cold Starts in AWS Lambda

thumbnail for this post

This article describes AWS Lambda—the dynamically scaled and billed-per-execution compute service. Instances of Lambdas are added and removed dynamically. When a new instance handles its first request, the response time increases, which is called a cold start.

Read more: Cold Starts in Serverless Functions.

When Does Cold Start Happen?

The very first cold start happens when the first request comes in after deployment.

After that request is processed, the instance stays alive to be reused for subsequent requests. There is no predefined threshold after the instance gets recycled, the empiric data show some variance of the idle period.

The following chart estimates the probability of an instance to be recycled after the given period of inactivity:

Probability of a cold start happening before minute X

An idle instance almost always stays alive for at least 25 minutes. Then, the probability of it being disposed slowly starts to grow and reaches 100% somewhere after 1 hour since the last request.

Read more: When Does Cold Start Happen on AWS Lambda?

How Slow Are Cold Starts?

The following chart shows the typical range of cold starts in AWS Lambda, broken down per language. The darker ranges are the most common 67% of durations, and lighter ranges include 95%.

Typical cold start durations per language

JavaScript, Python, Go, Java, and Ruby are all comparable: most of the time they complete within 500 milliseconds and almost always within 800 milliseconds. C# is a distinct underdog with cold starts spanning between 0.8 and 5 seconds.

View detailed distributions: Cold Start Duration per Language.

Does Package Size Matter?

The above charts show the statistics for tiny “Hello World”-style functions. Adding dependencies and thus increasing the deployed package size will further increase the cold start durations.

The following chart compares three JavaScript functions with the various number of referenced NPM packages:

Comparison of cold start durations per deployment size (zipped)

Indeed, the functions with many dependencies can be 5-10 times slower to start.

Does Instance Size Matter?

AWS Lambda has a setting to define the memory size that gets allocated to a single instance of a function. Are larger instances faster to load?

Comparison of cold start durations per instance size

There is no visible difference in cold start duration of different instance sizes.

Same comparison for larger functions: Cold Start Duration per Instance Size.

What Is The Effect Of VPC Access?

AWS Lambda might need to access resources inside Amazon Virtual Private Cloud (Amazon VPC). Configuring VPC access slows down the cold starts significantly:

Comparison of cold start durations of the same Lambda with and without VPC access

Some VPC-enabled cold starts are still fast, but very often they are much slower and can get up to 17 seconds.

View detailed distributions: Cold Start Duration of VPC-connected Lambda.

Responses
Visit the Github Issue to comment on this page