2 ms·

How do these perform for cold-starts? I remember one of the disadvantages of using web assembly for Workers was more spin-up time, but maybe they figured out a

• dom96 12d ago
  We’ve got some cold start numbers in our previous blog post: https://blog.cloudflare.com/python-workers-advancements/ https://blog.cloudflare.com/python-workers-advancements/. There is still more to do here and it’s what we will be focusing on next.
  • hbcondo714 12d ago
    Thanks, we've been using firecracker VMs with AWS MicroVM[1] and Fly.io Sprites[1] but interested in using Workers instead [1] https://news.ycombinator.com/item?id=48642510 https://news.ycombinator.com/item?id=48642510 [2] https://news.ycombinator.com/item?id=46557825 https://news.ycombinator.com/item?id=46557825
  • aeyes 12d ago
    The cold start numbers on that blog post show that its faster than AWS Lambda but your linked benchmark page [1] shows that Lambda is not only much faster but also much more consistent. [1] https://cold.picheta.me/#bare https://cold.picheta.me/#bare
• amenghra 12d ago
  In many cases, the cold-start time might not be visible to users. E.g. if you serve your static content from a CDN, maybe you have stale content in local storage you can show while fetching updated data. If it all happens on a sub-100ms timescale, it should feel quite instant?