Earlier quoted context omitted.
2x faster than Cloudflare Worker cold starts.
But monitoring fly.io from fly.io is a bit biased
Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render
11–20 of 43 posts
Re: Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render
#12Re: Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render
#13I wonder how much the open status server allocation plays a role in this case - they tested from 6 different location but its not clear if fpr example openstatus servers are in closer datacenters.
Re: Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render
#14I 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.
Submitters: If you want to say what you think is important about an article, that's fine, but do it by adding a comment to the thread. Then your view will be on a level playing field with everyone else's: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...
Re: Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render
#15I 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.
Re: Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render
#16>The primary region of our server is Amsterdam, and the fly instances is getting paused after a period of inactivity.
After they configured Fly to run nonstop, it outperformed everyone by 3x. But it seems like they're running the measurement from Fly's infrastructure, which biases the results in Fly's favor.
Also weird that they report p75, p90, p95, p99, but not median.
Re: Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render
#17Something is definitely up with Cloudflare's Johannesburg data centre. On particularly bad days, TTFB routinely reaches 1-3 seconds. Bypassing Cloudflare immediately drops this to sub 100ms.
In the past, I would have emailed support@cloudflare.com, but it seems that this channel is no longer available for free tier users. What is the recommended approach these days for reporting issues such as this?
Re: Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render
#18Very odd that AWS Lambda/Google Cloud Functions weren't tested. Those CF numbers are impressive though, they beat Lambda cold start by a mile.
Re: Monitoring latency: Cloudflare Workers vs Fly vs Koyeb vs Railway vs Render
#19e.g. if you add prisma connecting to postgres, presumably there's extra latency to create the client. for the fly app, you have a server reusing the client while it's warm. presumably for the cloudflare worker, you're recreating the client per request, but im not 100% on that. how would the latency change then for cold vs warm, and on the other platforms?