Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I would love to know what the margin boost is to AWS as a result of Graviton. It's cheaper to customers but I have to imagine better margins to them - so kind of a win/win. It's just amazing how they're pushing it out to every AWS service at this point. We transitioned over our RDS instances to Graviton this last weekend and have a nice performance boost with ~10% savings.

Disclosure as I'm Co-Founder and CEO of Vantage - but we'll likely be adding Graviton recommendations to our suite of cost saving recommendations on https://www.vantage.sh/ to give per resource views of potential savings (i.e. you can save X% on this Lambda function based upon the costs we saw by switching to Graviton, etc.)



From folks I know at AWS, services are all being heavily pushed to use Graviton to run their services, to the point of having to justify why they couldn't. The cost savings internally are just as significant.


I am now going to go down the rabbit hole of arm specific bugs in the libraries I use because so far all of the applications I dev (arm ubuntu) have never encountered any bugs.

Yay free money!


I think they will transition all services that do not expose infrastructure (think i.e. Cognito, Pinpoint, VPC, Api Gateway, CloudFormation, ...) ASAP.


With Nitro they disclosed that every EC2 machine deployed in the last 5+ years has at least one ARM chip because each server has a nitro card.

So reading the tea leaves... the first generation of EC2 ARM (a1) could have been almost as simple as two nitro cards hooked together.

Graviton2 is likely a bigger chip than what they're sticking on Nitro cards, but if Graviton1 was just the overhead for each Intel machine...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: