Live data from Hacker News

Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render

openstatus.dev

1–10 of 43 posts

Re: Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render

#7
post #6

I feel like this title is misleading compared to the original article. (cc @dang) Fly.io without cold starts (which is a one-line configuration change) is 2x faster than Cloudflare Workers.

2x faster than Cloudflare Worker cold starts.

Re: Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render

#8
I would love to see Wasmer Edge in the next comparison!

A summary for the lazy readers:

  * Cloudflare workers outperforms the rest by a big margin (~80ms avg)
  * Fly.io cold starts are not great for the Hono use case (~1.5s avg)
  * Koyeb wraps the requests behind Cloudflare to optimize latency (150ms best case)
  * Railway localized the app in one region (80ms best case, ~400ms rest)
  * Render has some challenges scaling from cold (~600ms avg)
In my opinion, this shows that all platform providers that uses Docker containers under the hood (Fly, Koyeb, Railway, Render) only achieve good cold starts by never shutting down the app. The ones that they do, can only achieve ~600ms startup times at best.

Re: Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render

#9
post #6

I feel like this title is misleading compared to the original article. (cc @dang) Fly.io without cold starts (which is a one-line configuration change) is 2x faster than Cloudflare Workers.

2x faster than Cloudflare Worker cold starts.

But monitoring fly.io from fly.io is a bit biased
Post reply on HN