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.
Switching to AWS Graviton slashed our infrastructure bill
11–20 of 140 posts
Re: Switching to AWS Graviton slashed our infrastructure bill
#12Cloud 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.
Re: Switching to AWS Graviton slashed our infrastructure bill
#13The link throws a 503 rn. I wonder what would be the reason
Re: Switching to AWS Graviton slashed our infrastructure bill
#14Cloud 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.
Re: Switching to AWS Graviton slashed our infrastructure bill
#15Cloud 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.
Re: Switching to AWS Graviton slashed our infrastructure bill
#16The 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. :-)
Re: Switching to AWS Graviton slashed our infrastructure bill
#17Imagine how much they'd save by not using AWS in the first place
Re: Switching to AWS Graviton slashed our infrastructure bill
#18Cloud 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
#19Earlier 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.
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
#20I 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…