Still having your own hardware seems so much cheaper. Maybe even just for dev/uat environments? Every big corporate I have worked at has lower cost of capital than Amazon, and yet they want to move to AWS. I just dont understand it.
> I just don’t understand it Maintaining and updating your own hardware comes with so much operational overhead compared to magically spinning up and down resources as needed. I don’t think this really needs to be said.
Cloud VM benchmarks 2026
71–80 of 165 posts
Re: Cloud VM benchmarks 2026
#72Disclosure: I work on VMs at Google Compute Engine :) This was a really, really good write-up. I appreciated the breadth of VMs tested and the spread of benchmarks. A few random observations: 1. Turin is a beast. 2. The data on price-performance makes Hetzner look really fantastic, especially for small scale projects where region placement doesn’t matter much and big bursty scaling isn’t required. 3. I think the firs…
Hetzner really shines with their dedicated stuff.
Re: Cloud VM benchmarks 2026
#73I just ran some massive tests on our own CI. I use AMD Turin for this on gcp, which was noted as one of the fastest ones in the article. The most insane part here is that the AMD EPYC 4565p can beat the turin's used on the cloud providers, by as much as 2x in the single core. Our tests took 2 minutes on GCP, 1 minute flat on the 4565p with its boost to 5.1ghz holding steady vs only 4.1ghz on the gcp ones. GCP charges…
This proc is a hidden gem.
For most workloads it’s not just the most performant, but also the best bang-for-buck.
Re: Cloud VM benchmarks 2026
#74Earlier quoted context omitted.
> No theory. No fluff. Just production. ChatGPT tells me "no theory, no fluff" all the time :D
Where do you think it learned that phrasing from?
""" No warning. No traffic spike. Just… more money gone.
That’s when I finally looked at Hetzner.
I’ve seen too many backend systems fail for the same reasons — and too many teams learn the hard way.
So I turned those incidents into a practical field manual: real failures, root causes, fixes, and prevention systems.
No theory. No fluff. Just production. """
It's clearly slop, they immediately use effectively the same one again:
""" That last line isn’t a joke. There were charges I genuinely couldn’t explain. Elastic IPs we forgot to release. Snapshots from instances that no longer existed. CloudFront distributions someone set up for testing. """
No, human writers don't repeat this pattern every single paragraph. They use it at most across in a whole article.
Re: Cloud VM benchmarks 2026
#75I just ran some massive tests on our own CI. I use AMD Turin for this on gcp, which was noted as one of the fastest ones in the article. The most insane part here is that the AMD EPYC 4565p can beat the turin's used on the cloud providers, by as much as 2x in the single core. Our tests took 2 minutes on GCP, 1 minute flat on the 4565p with its boost to 5.1ghz holding steady vs only 4.1ghz on the gcp ones. GCP charges…
Both Datapacket & OVH have the 4565p. This proc is a hidden gem. For most workloads it’s not just the most performant, but also the best bang-for-buck.
Re: Cloud VM benchmarks 2026
#76Re: Cloud VM benchmarks 2026
#77Re: Cloud VM benchmarks 2026
#78Earlier quoted context omitted.
Where do you think it learned that phrasing from?
Not from people using that same phrasing twice within a few sentences. """ No warning. No traffic spike. Just… more money gone. That’s when I finally looked at Hetzner. I’ve seen too many backend systems fail for the same reasons — and too many teams learn the hard way. So I turned those incidents into a practical field manual: real failures, root causes, fixes, and prevention systems. No theory. No fluff. Just produ…
I'm just irked that it's being called out for AI slop because "I feel it in my bones!!"
There's a good chance it was written using AI -- should that matter? If the content is wrong/sucks, say that instead. If you're going to dismiss all AI assisted writing: good luck in the next decade.
Re: Cloud VM benchmarks 2026
#79Earlier quoted context omitted.
the 140/mo is for 3x less vcpu, so $420/mo savings if you use all those same cores. sorry for the poor comparison wording there. in a few months already up to $1300+ by 6 months already paid the machine. colo fees are cheap if you need more than just 1u. even with a 50-100 fee you easily get way more performance and come ahead within a year
> by 6 months already paid the machine. You originally said “a couple months” but now it’s 6 months and assumption of $0 collocation fees which isn’t realistic In my experience situations rarely call for precisely 32 cores for a fixed period of 3 years to support calculations like this anyway. We start with a small set of cloud servers and scale them up as traffic grows. Today’s tooling makes it easy to auto scale th…
Re: Cloud VM benchmarks 2026
#80I just ran some massive tests on our own CI. I use AMD Turin for this on gcp, which was noted as one of the fastest ones in the article. The most insane part here is that the AMD EPYC 4565p can beat the turin's used on the cloud providers, by as much as 2x in the single core. Our tests took 2 minutes on GCP, 1 minute flat on the 4565p with its boost to 5.1ghz holding steady vs only 4.1ghz on the gcp ones. GCP charges…
For €104/mo you can get a 16-core Ryzen 9 7950X3D (basically identical to your 4565p) w/ 128GB DDR5, 2x2TB PCIE Gen4 SSD.
That's not to say you're wrong about dedicated being much better value than VPS on a performance per dollar basis, but the markup that the European companies charge is much, much lower compared to what they'd charge in the US.
In this instance you're looking at a ~17 month payback period even ignoring colo fees. Assuming a ~$100 colo fee that sibling comment suggested, you're looking at closer to 8 years.