AWS Lambda Execution Visualizer

Understand how Lambda manages execution environments based on request patterns

Simulation Controls
Adjust the request rate, execution time, and cold start duration to see how Lambda scales
Execution Environments
Each box represents a Lambda execution environment. Watch how they're created and reused.
No execution environments yet. Start the simulation to see them appear!
0
Total Requests
0
Completed
0
Active Environments
0
Peak Environments
Recent Requests
Latest 10 requests and their processing status
No requests yet. Start the simulation!
How AWS Lambda Works
Warming (Cold Start)

New execution environments need time to initialize before they can process requests. Cold start times vary based on runtime, memory, and code complexity.

Busy (Processing)

Environments actively processing requests. Each can handle one request at a time.

Idle (Available)

Ready environments that can immediately process new requests without cold start.

Key Insights:

  • • Higher request rates require more concurrent execution environments
  • • Longer execution times keep environments busy longer, requiring more instances
  • • Longer cold start times delay request processing and may require more environments
  • • AWS automatically scales environments up and down based on demand
  • • Reusing warm environments avoids cold start delays