From Go on EC2 to Fly.io: +fun, −$9/mo

Re:From Go on EC2 to Fly.io: +fun, −$9/mo by ZephyrBlu on Monday February 27, 2023 @01:40AM (#34953738)

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.

[ Parent | on HN ]

Re:From Go on EC2 to Fly.io: +fun, −$9/mo by re-thc on Monday February 27, 2023 @02:56AM (#34954097)

Is this due to the network i.e. you get routed to a different server or due to CPU sharing?

[ Parent | on HN ]

Re:From Go on EC2 to Fly.io: +fun, −$9/mo by ZephyrBlu on Monday February 27, 2023 @03:14AM (#34954192)

I 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.

[ Parent | on HN ]

Re:From Go on EC2 to Fly.io: +fun, −$9/mo by achempion on Monday February 27, 2023 @03:08AM (#34954161)

isn't the whole selling point of fly is edge servers which supposed to reduce latency

[ Parent | on HN ]

Re:From Go on EC2 to Fly.io: +fun, −$9/mo by re-thc on Monday February 27, 2023 @07:06AM (#34955469)

Sure, 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.

[ Parent | on HN ]

Re:From Go on EC2 to Fly.io: +fun, −$9/mo by marcinzm on Monday February 27, 2023 @07:50AM (#34955793)

So 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?

[ Parent | on HN ]

Re:From Go on EC2 to Fly.io: +fun, −$9/mo by ignoramous on Monday February 27, 2023 @03:41AM (#34954313)

* * *

[ Parent | on HN ]