Google Cloud Functions: Cold Start Duration per Instance Size

Google Cloud Functions have a setting to define the memory size that gets allocated to a single instance of a function. The CPU resources are allocated proportionally to the memory. So, in theory, larger instances could start faster.

However, there seems to be no significant speed-up of the cold start as the instance size grows.

Here is the comparison for a “Hello-World” JavaScript function:

Comparison of cold start durations per instance size, no dependencies

Here is the same comparison for a JavaScript function with 14 MB (zipped) of NPM packages:

Comparison of cold start durations per instance size, 14 MB (zipped) of dependencies

Here is the same comparison for a JavaScript function with 35 MB (zipped) of NPM packages:

Comparison of cold start durations per instance size, 35 MB (zipped) of dependencies

All of the charts shows an advantage of larger instance sizes for cold starts, and the difference increases with the size of a deployment package.

Go back to Cold Starts in Google Cloud Functions.


Cloud developer and researcher.
Software engineer at Pulumi. Microsoft Azure MVP.

comments powered by Disqus