.NET Core 3.0 AWS Lambda Benchmarks and Recommendations

Photo by Jason Chen on Unsplash

ReadyToRun

IL Trimming

Tiered Compilation

Quick JIT

Test Function Code

The Variations

  • rReadyToRun
  • t — IL Trimming
  • c — Tiered Compilation
  • qQuick JIT

Graphs For Ants

Cold Starts

Here is the interactive version.

Initliazation + Overhead

Here is the interactive version.

Warm Starts

Here is the interactive version.

Summary

Recommendations

  • Don’t bother using 2.2, just go straight to 3.0.
  • Keep using 2.1 if you want maximum performance.
  • If you use 3.0, add more memory for more performance!
  • Make sure you have tiered compilation turned off to avoid 15–20 seconds of lower performance after the cold start.
  • Don’t use IL Trimming unless you need it to fit inside the Lambda package size limit.
  • When using 3.0, have ReadyToRun enabled and everything else disabled.

--

--

--

Serverless Engineer @ Stedi | AWS Community Builder

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

TDD With URM and Kotlin

Gauging your team’s efforts, using Velocity

Read Write Quorums

Implementation inverse matrix for images — numpy

Continuous Deployment via GitLab, Jenkins, Docker and Slack

How to Install an Apache Web Server on CentOS 8

Top 10 Xamarin Interview Questions and Answers — Digitally Mag

How to Install and Configure NFS Server and Client

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Zac Charles

Zac Charles

Serverless Engineer @ Stedi | AWS Community Builder

More from Medium

.NET on AWS — Data Persistence using RDS

Custom Docker image as a lambda function.

Invoke AWS Lambda Function programmatically using .NET, C# and AWS Lambda SDK

Creating S3 Upload Presigned URL with API Gateway and Lambda