About 4ms for us. However, we chose our data centres on both ends very carefully... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		rolleiflex on March 5, 2020 \| parent \| context \| favorite \| on: Google Kubernetes Engine is introducing a cluster ... About 4ms for us. However, we chose our data centres on both ends very carefully. There are tables online you can find that for those pings, one such is here: https://medium.com/@sachinkagarwal/public-cloud-inter-region... However this means we are paying for egress on both sides. This was something we chose to eat due to GCP Kubernetes, but considering today’s changes, it probably no longer makes sense.

vasco on March 5, 2020 | [–]

So you decide to eat egress costs in perpetuity, which will scale as you go, but a one time increase of $70 per month is enough to make you go back? What are you even trying to optimize for?

sheeshkebab on March 5, 2020 | [–]

sheesh, the lengths you guys went to build that monstrosity.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact