There are different Coretex series that optimize for different things- A and X for applications (phones, cloud compute, SBCs, desktops and laptops), M for microcontrollers, and R for realtime.
This doesn't apply if the company has an ARM founder and/or architecture license. (I think that's what they're called) Eg- Apple and their M series SOCs are not Coretex cores, but share the base instruction set- but only if Apple wants it to.
AWS with Nitro v3+ iirc supports TPM, meaning I can attest my VM state via an Amazon CA. I know ARM has been working a lot with Rust, and it shows - binfmt with qemu-user mean I often forget which architecture I'm building/running/testing as the binaries seem to work the same everywhere.
eg c7i-flex.large, etc.
Just like AMD Epyc.
> and 5x larger cache,
Larger than what ? 16k ?
spwa4•2mo ago
dpoloncsak•2mo ago
spwa4•1mo ago
dpoloncsak•1mo ago
DonHopkins•1mo ago
locknitpicker•1mo ago
AWS management is the customer.
Higher compute density, lower infrastructure costs, and higher performance. Those are data center selling points.
The truth of the matter is that your average external customer doesn't really care about CPU architectures if all they are doing is using serverless offerings, specially AWS Lambdas handling events. They care about what it costs them to run the services. AWS management decide if the returns on their investment is paying off and helps them lower costs and improve margins.