AWS Lambda Web Functions keep billing memory ~7 minutes after the last request
Web page · https://easel.sh/blog/lambda-web-functions-idle-memory
First seen by Oriel on .
AI summary
Easel tested AWS Lambda Web Functions, found prolonged idle-memory billing costly for unpredictable application traffic, and chose self-operated shared compute, which was faster in its early benchmarks.
- Web Functions handled 300 concurrent requests and served a new function in under nine seconds, but environments remained active 313–411 seconds after their last requests.
- Memory represented approximately 88% of calculated compute and request costs; terminating environments after 10 seconds cut metered time roughly 20× but registered runtime failures.
- Easel’s hosts share capacity among applications, route overflow to traditional Lambda, and provide control over scheduling and resource allocation.
- On the same Next.js 16 application, Easel achieved 1.5–3× faster median warm requests, while 20,000 chained SHA-256 operations ran in 29.2ms versus 43.8ms.
- After 12 minutes idle, Easel’s cold starts took 216–250ms versus AWS’s 810–854ms, though tests covered one region, two cold-start trials, and different hardware.
#aws lambda #serverless #cloud economics #web performance
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Hacker News: 77, latest observation ; +67 over observed period since
Comments
Comment count reported by the source.
- Hacker News: 31, latest observation ; +29 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Hacker News | 50470445 | https://www.easel.sh/blog/lambda-web-functions-idle-memory Read discussion |