Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

openstatus.dev

Post reply on HN
Print view View original

41–43 of 43 posts

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

#41

Post by mtlynch »

catlifeonmars wrote: post #31
mtlynch wrote: post #16

I was surprised to see such miserable measured latency to Fly, but then I saw this note: > 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…

I’m not sure what’s customary in most places, but in my experience you base most things off of avg and p99 and then you can use other percentiles to interpolate the shape of the distribution in the event you need a better model (you usually don’t). Of course I’m sure this sort of thing varies wildly by use case.

I admit that I don't deal a lot with latency measurements, but my memory from working at Google was that we focused on p50, p95, and p99. That was six years ago, and it wasn't my focus there, so it's possible I'm misremembering (especially based on all the responses saying I'm the weirdo for expecting p50).

Looking at Google's SRE book, they use p50, p85, p95, and p99, so it's possible I'm misremembering or that Google uses unusual metrics:

https://sre.google/sre-book/service-level-objectives/#fig_sl...

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

#42

Post by catlifeonmars »

mtlynch wrote: post #41
catlifeonmars wrote: post #31

Earlier quoted context omitted.

I’m not sure what’s customary in most places, but in my experience you base most things off of avg and p99 and then you can use other percentiles to interpolate the shape of the distribution in the event you need a better model (you usually don’t). Of course I’m sure this sort of thing varies wildly by use case.

I admit that I don't deal a lot with latency measurements, but my memory from working at Google was that we focused on p50, p95, and p99. That was six years ago, and it wasn't my focus there, so it's possible I'm misremembering (especially based on all the responses saying I'm the weirdo for expecting p50). Looking at Google's SRE book, they use p50, p85, p95, and p99, so it's possible I'm misremembering or that Goog…

I wasn’t aware of the Google SRE book. Thanks, I’ve bookmarked it!

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

#43

Post by catlifeonmars »

tibozaurus wrote: post #39
catlifeonmars wrote: post #30

Those Fly.io p99 latencies are atrocious. 2.6s P99 compared to CloudFlare 1.0s. Neither one seems particularly great at first glance, but the CloudFlare worker latency does seem on par with Lambda from previous experience (I have not tested Lambda@Edge or CloudFront Functions).

It's due to cold start on default preset when creating an app if you are running the app continuously it's good

I’m not familiar with the scaling behavior of Fly.io. Do you still hit cold starts on scale up?
Post reply on HN