Skip to content
Trending storyPast story

Easel measures Lambda idle billing on Web Functions, moves to self-hosted compute

1 report1 sourceupdated 4 days ago

What happened

AI digest

Easel tested AWS Lambda Web Functions and found execution environments stayed alive 313 to 411 seconds after the last request, billing memory the whole time, with no idle timeout setting. Memory was about 88% of the compute and request cost Easel calculated. Easel moved to self-hosted compute and keeps traditional Lambda only for overflow traffic. On the same Next.js 16 app, hot requests after the change had a median latency 1.5 to 3 times faster, and cold starts after 12 idle minutes were about 3.5 times faster.

Written by AI from the coverage · updated 4 days ago

Coverage

Follow the reports to see the story from different sides.

Nov 13
  1. Hacker News front page
    AWS Lambda Web Functions keep billing memory ~7 minutes after the last request

    Easel 实测 AWS Lambda Web Functions 发现,执行环境在最后一次请求后仍存活 313–411 秒并持续计收内存费用,且无空闲超时配置;内存约占其测算计算与请求成本的 88%。Easel 因此改为自建计算、仅用传统 Lambda 承接溢出流量,同一 Next.js 16 应用热请求中位延迟快 1.5–3×,闲置 12 分钟后冷启动快约 3.5×。

Heat over time

Heat now 3·Comparable peak 10(Nov 13 02:00)·Comparable change over 24 hours -49%

02.557.510Nov 1302:00Nov 1317:00Nov 1409:00Nov 1500:00

The trend only compares accounts observed without gaps, so its range may be smaller than the current heat. Hover or tap the chart for each hour; the left and right arrow keys step through it.