Google Cloud Functions

When Does Cold Start Happen on Google Cloud Functions?

The very first cold start happens when the very first request comes in after deployment. After that request is processed, the instance stays alive for the time being to be reused for subsequent requests.

Read more...

Google Cloud Functions: Cold Start Duration per Language

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

Read more...

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.

Read more...

Comparison of Cold Starts in Serverless Functions across AWS, Azure, and GCP

AWS Lambda, Azure Functions, and Google Cloud Functions compared in terms of cold starts across all supported languages

Read more...

Cold Starts in Google Cloud Functions

Running GA and Beta languages on different instance sizes

Read more...

Less Frequent Cold Starts in Google Cloud Functions

Google keeps idle instances of Cloud Functions alive for many hours.

Read more...

Visualizing Cold Starts

Serverless cold starts illustrated with animated GIFs.

Read more...

Serverless at Scale: Serving StackOverflow-like Traffic

Scalability test for HTTP-triggered serverless functions across AWS, Azure and GCP

Read more...

From 0 to 1000 Instances: How Serverless Providers Scale Queue Processing

Comparison of queue processing scalability for FaaS across AWS, Azure and GCP

Read more...

Serverless: Cold Start War

Comparison of cold start statistics for FaaS across AWS, Azure and GCP

Read more...