4 ms·
My main gripe is the wild variation in response time. My server response time seemed to vary from <100ms to >300ms for the same operation.
by ZephyrBlu 4y ago
My main gripe is the wild variation in response time.
My server response time seemed to vary from <100ms to >300ms for the same operation.
- re-thc 4y agoIs this due to the network i.e. you get routed to a different server or due to CPU sharing?
- achempion 4y agoisn't the whole selling point of fly is edge servers which supposed to reduce latency
- re-thc 4y agoSure, but what's edge? The world is big. Can't have servers everywhere (ok, maybe Cloudflare is close). It's possible due to routing decisions that you get sent to a "different edge" at different times.
- marcinzm 4y agoSo what's the point then? 250ms is enough to literally send traffic to the other side of the world. So why bother with edges if you can just have a single server where most of your customers are and get the same latencies?
- ZephyrBlu 4y agoI thought it could have been because of a shared CPU at first as well, but I upgraded to dedicated CPUs and it didn't make a difference. I don't know whether this is a platform issue with Fly or something else, but it was kind of annoying to have such a high variation with seemingly no way to fix it.
- ignoramous 4y agofwiw, for non-html workloads we serve (nodejs) with shared-cpu (several 100 requests per second), the latencies (p50, p75) remain consistent.