AWS, Azure, and GCP respond to cloud report
cockroachlabs.com
AWS, Azure, and GCP respond to cloud report
1–10 of 35 posts
Re: AWS, Azure, and GCP respond to cloud report
#2Is there a reliability/availability report that covers multiple months (VM uptime, PaaS services, etc)?
I've personally seen the reliability differences of services in Azure vs AWS for example.
Re: AWS, Azure, and GCP respond to cloud report
#3Previous thread: https://news.ycombinator.com/item?id=21804939
Re: AWS, Azure, and GCP respond to cloud report
#4Azure also offers ephemeral OS disks that can speed up OS perf. This probably won't make any difference in a database test (unless they store their data ephemerally too, which...). But still, another thing to consider.
Re: AWS, Azure, and GCP respond to cloud report
#5Previous thread: https://news.ycombinator.com/item?id=21804939
This is a new post that updates the previous post with cloud vendor responses.
Re: AWS, Azure, and GCP respond to cloud report
#6> Azure offers a large number of configuration options that can be tricky to get right
That's basically the summary of Azure. I think all that complexity ends up hurting more than it helps, not just on the end user side, but in terms of lower reliability from the provider side.
Re: AWS, Azure, and GCP respond to cloud report
#7What a load of nonsense. So cloud provides X doesn’t like the test because the defaults of their services do not provide the best performance and on top of that the benchmark used doesn’t present them with the result that shows them in the best possible light.
It’s like listening to failed beauty pageant contenders
Re: AWS, Azure, and GCP respond to cloud report
#8Since you're one of the authors: TPC_RR is a typo.
Re: AWS, Azure, and GCP respond to cloud report
#9Thanks Cockroach team!
I'm very excited about the possibility of moving to you guys, especially since it's a drop-in replacement for Postgres. The one thing holding us back today is postgis replacement. We rely heavily on it for location calculations and route path saving.
Re: AWS, Azure, and GCP respond to cloud report
#10Since you're one of the authors: TPC_RR is a typo.
Disclosure: I work on Google Cloud (and also commented on Cockroach’s original draft post, that this is a follow up to).
Edit: I am a chump, I misread TPC_RR as TCP_RR and responded. Leaving this here for shame. Thanks to jsolson for pointing out my mistake.
I’m not sure if the post was edited, but TCP_RR is definitely not a typo. You may be more used to seeing TCP_CRR which opens a new connection and then a round trip, but for raw network latency netperf’s TCP_RR benchmark is probably the best tool available.