Live data from Hacker News

Switching to AWS Graviton slashed our infrastructure bill

squeaky.ai

11–20 of 140 posts

Re: Switching to AWS Graviton slashed our infrastructure bill

#11
post #2

Cloud cost optimisation is underrated. In the companies I've worked in nobody has really given a shit (at least not under normal economic circumstances). In the industry there's a strong avoidance of ARM compute instances for no good reason. If I were building from scratch today I would definitely go with Graviton.

If I started to build today I'd build and host my own servers, or go with servers from ionos. Cloud is very expensive.

Re: Switching to AWS Graviton slashed our infrastructure bill

#12
post #2

Cloud cost optimisation is underrated. In the companies I've worked in nobody has really given a shit (at least not under normal economic circumstances). In the industry there's a strong avoidance of ARM compute instances for no good reason. If I were building from scratch today I would definitely go with Graviton.

We are building everything for arm and I've surprised if other large companies aren't optimising for it.

Re: Switching to AWS Graviton slashed our infrastructure bill

#14
post #2

Cloud cost optimisation is underrated. In the companies I've worked in nobody has really given a shit (at least not under normal economic circumstances). In the industry there's a strong avoidance of ARM compute instances for no good reason. If I were building from scratch today I would definitely go with Graviton.

I think the main reason is "I want to run the same binaries locally that I run in the cloud," and it's a pretty valid one. However, it's also an expensive one sometimes.

Re: Switching to AWS Graviton slashed our infrastructure bill

#15
post #2

Cloud cost optimisation is underrated. In the companies I've worked in nobody has really given a shit (at least not under normal economic circumstances). In the industry there's a strong avoidance of ARM compute instances for no good reason. If I were building from scratch today I would definitely go with Graviton.

If I started to build today, I'd definitely go for Hetzner Cloud. There is zero possibility that I get surprised by a large bill.

Too bad Hetzner doesn't have cheaper Arm servers available. Their Ampere pricing is not really convincing.

Re: Switching to AWS Graviton slashed our infrastructure bill

#16
post #8

The marriage of an all arm64 dev env and a Graviton op env is a match made in heaven. Everyone please do this so we collectively fix all the things to work with this. :-)

It is unless you're the first poor soul to embark on the journey with lots of x86_64 buildup. Having said that, it's been fun though so far. Managed to migrate our dev local k8s toolchain and been using buildx to make multiarch images and manifests for our internal stuff.

Re: Switching to AWS Graviton slashed our infrastructure bill

#18
post #2

Cloud cost optimisation is underrated. In the companies I've worked in nobody has really given a shit (at least not under normal economic circumstances). In the industry there's a strong avoidance of ARM compute instances for no good reason. If I were building from scratch today I would definitely go with Graviton.

I think the main reason is "I want to run the same binaries locally that I run in the cloud," and it's a pretty valid one. However, it's also an expensive one sometimes.

Anecdotally, this is starting to shift with M1 MacBooks, Graviton is looking more attractive for precisely that architecture parity reason for teams using majority M1 devices.

Re: Switching to AWS Graviton slashed our infrastructure bill

#19
post #9

Earlier quoted context omitted.

If I started to build today, I'd definitely go for Hetzner Cloud. There is zero possibility that I get surprised by a large bill.

I feel it's currently in beta, I've tried it and apparently I can't create more than a few instances because my account is "too new", without a clear way to remove that limit so you're right, can't have a large bill if you can't even create 10 instances.

Did you try writing them and asking them to increase the limit?

No cloud provider will give you the option to create as many instances as there are available ones, they all have limits from the get-go. Usually you have to write them/fill out some form if you want to go above the standard limit, Hetzner Cloud as well.

Re: Switching to AWS Graviton slashed our infrastructure bill

#20

I found graviton to be a mixed bag. It was certainly extremely fast when using the very high end instances and I tested it successfully using a Rust based message queue system I was writing and it got some ridiculously fast number like 8 million messages a second, from memory, using the fastest possible graviton instance (this was about 18 months ago). I did try to switch some of my database servers to it a couple of…

I'm curious about that Rust-based message queue system
Post reply on HN