41–50 of 124 posts
I remember that GCP claimed they will follow Moore's Law and drop the price for the same instance type over time. It was just BS marketing, unfortunately I believed them.
I remember that GCP claimed they will follow Moore's Law and drop the price for the same instance type over time. It was just BS marketing, unfortunately I believed them.
Earlier quoted context omitted.
Yeah, and without comparing spot/interruptible prices, these results are meaningless for me.
You wouldn't typically run your database VMs on spot/interruptible instances.
> ...in 2018, AWS outperformed GCP by 40%, which we attributed to AWS’s Nitro System present in c5 and m5 series... In 2020, we see a return to similar overall performance in each cloud. How did GCP and Azure catch-up to AWS Nitro in one year which IIRC is a coming together of minimalistic micro-vms, hardware-accelerated network and IO cards, hardware offload for encryption and other maintenance tasks... a work that…
Amazon's original fix reduced performance substantially, which lot's of people noticed, but no one knew why till the vulnerabilities were announced.
Meanwhile Google built a clever workaround which minimized the pain. It was really a mic-drop moment from Google and I wish someone would dig in deep and tell the whole story.
At this point I'm sure AWS has merged Google's patches, but it showed how much Google was investing in their GCP offerings.
I wish they had benchmarked the arm instances on AWS, I'd like to see a 3rd party validate AWS's claims about performance.
Looking at the Azure networking numbers I wonder if they got their configs correctly optimized. Azure networking was always tricky to get best performance when I used it heavily at my last co.
No, I contacted them directly after seeing this report and confirmed they did not even use accelerated networking (which is a free, but opt-in service on Azure), much less things like placement proximity groups (which only recently went public). So machines were communicating across availability zones (separated physically by miles and logically by additional networking layers) and a bunch of networking was happening…
They should also have included oracle which will soon surpass google (making it 5th most popular) cloud
> ...in 2018, AWS outperformed GCP by 40%, which we attributed to AWS’s Nitro System present in c5 and m5 series... In 2020, we see a return to similar overall performance in each cloud. How did GCP and Azure catch-up to AWS Nitro in one year which IIRC is a coming together of minimalistic micro-vms, hardware-accelerated network and IO cards, hardware offload for encryption and other maintenance tasks... a work that…
Meltdown and Spectre did a real number on the c5 and m5 instance types. Amazon's original fix reduced performance substantially, which lot's of people noticed, but no one knew why till the vulnerabilities were announced. Meanwhile Google built a clever workaround which minimized the pain. It was really a mic-drop moment from Google and I wish someone would dig in deep and tell the whole story. At this point I'm sure…
They should also have included oracle which will soon surpass google (making it 5th most popular) cloud
https://www.platformonomics.com/2019/02/follow-the-capex-clo...
"Google’s incremental CAPEX spend in 2018 is about what cloud pretender Oracle has spent on CAPEX throughout their entire history."