AWS Lambda Web Functions Fail Idle-Cost Test
Easel measured 313–411 seconds of post-request idle time during which Lambda Web Functions continued billing memory. The company says its own compute delivered faster warm responses and roughly 3.5× faster cold starts.
Lambda Web Functions’ active-CPU billing is attractive, but persistent memory charges make quiet workloads harder to price than AWS’s serverless pitch suggests.
- –Memory represented about 88% of Easel’s test costs.
- –A 300-request burst provisioned roughly 37 environments, adding billing overhead beyond actively serving instances.
- –There is no configurable idle timeout, limiting control for low-traffic applications.
- –For I/O-heavy, consistently busy APIs, the model may still outperform traditional Lambda functions.
- –Easel’s results highlight why developers should model real traffic patterns instead of trusting headline pricing examples.
DISCOVERED
3h ago
2026-11-12
PUBLISHED
7h ago
2026-11-12
RELEVANCE
AUTHOR
seanw265