back to home

maxday / lambda-perf

Lambda Cold Starts analysis, updated daily

View on GitHub
603 stars
54 forks
49 issues

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing maxday/lambda-perf in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/maxday/lambda-perf)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

🔄 Continous Lambda Cold Starts Benchmark **TL;DR:** 👀 to https://maxday.github.io/lambda-perf/ to see the benchmark result: Why? There are already a lot of blog posts talking about Lambda Cold Starts performance per runtime but I could not find any always up-to-date information. That's why I decided to create this project: data is always up to date as the benchmark is running daily. How does it work? Architecture diagram Step 1 An ultra simple hello-world function has been written in each AWS supported runtime: • • • • • • • • • • • • • • • • • • • • • • in addition to the following custom runtimes: • on • on • on • on • on • on • on • on • on • on • on • on • on • on • on • on • on • on (with and without layer) • on • on • on Each of this function is packaged in a zip file, uploaded to a S3 bucket. Note that the SnapStart feature is no longer benchmarked, as using it with a simple hello-world application may not represent a meaningful use case. Step 2 Every day, each function is freshly grabbed from S3, deployed and invoked 10 times as cold starts. Then the REPORT log line containing the init duration, max memory used and other useful information is saved to a DynamoDB table. Step 3 After all these invocations, all information stored in DynamoDB is aggregated and a new JSON file is created, then commited to this repo. ie: https://github.com/maxday/lambda-perf/blob/main/data/2022/2022-09-05.json Step 4 A static website, hosted on GitHub pages here: https://maxday.github.io/lambda-perf/ fetches this JSON file and displays the result in a (nice?) UI. Step 5 Hack/Fork/Send PR and create your own benchmarks! Disclaimer ⚠️ This project is not associated, affiliated, endorsed, or sponsored by any companies nor have they been reviewed tested or certified by any company.