AWS Lambda Web Functions keep billing memory ~7 minutes after the last request
A development team at Easel found that AWS Lambda Web Functions accrue memory billing for 5-7 minutes after the last request, leading them to build their own compute infrastructure. Their custom solution proved to be both more cost-effective and faster than the AWS offering.
Why it matters
This highlights a common challenge in cloud cost optimization and the trade-offs between managed serverless services and custom infrastructure.
Lambda Web Functions kept billing memory for 5–7 minutes after the last request, so we built our own compute. On the same Next.js app, it answered warm requests 1.5–3× faster and cold-started about 3.5× faster.
When AWS announced Lambda Web Functions in October, I was excited.
At Easel , we'd spent months building infrastructure to run web applications efficiently on traditional Lambda. Native HTTP servers, concurrent requests, and active CPU billing sounded like exactly what we'd been looking for.
If Web Functions worked the way we hoped, we could potentially replace a substantial amount of our custom infrastructure.
A few weeks later, we'd decided to run our own compute instead. And as it turns out, our own infrastructure was faster, too.
Our initial experiments were promising. Web Functions handled 300 concurrent requests without errors, and a new function was serving requests in under nine seconds.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in