Amazon EC2 M9g Instances

Why: you might be concerned with network connectivity (you don't get to choose which data center you launch in and it might not be exactly equal), noisy neighbors on shared hosts, etc. if you're measuring for networking, you probably are spinning ups separate accounts/using a bank of accounts and something in every az until you find what you're looking for.

This AWS EC2 site is just an open-source project and site we maintain for the benefit of the community. So it's not directly our business but it promotes our brand and is just a helpful site that I think should exist. It's very popular and has been around for about 15 years now.

Our main business hosted on the main domain of https://www.vantage.sh/ is around cloud cost management across 25 different providers (AWS, Azure, Datadog, OpenAI, Anthropic, etc) and the use-cases there about carving up one bill and showing specific costs back to engineers for them to be held accountable to, take action on, etc. Cloud costs and their impact on companies' margins is a big enough problem for vendors like us to exist and we're one player in a larger market.

We'd greatly appreciate contributions!

Parent comment made a low quality joke that lacked substance.

The cobbler's children have no shoes.

While I know this thread will turn into some noisy whack-a-mole bit of nonsense, an easy comparison is the c8g.2xlarge vs the c8i.2xlarge. The former is Graviton 4 vs Granite Rapids in the latter. Otherwise both 16GB, 15Gbps networking, and both are compute optimized, 8 vCPU machines.

Performance is very similar. Indeed, since you herald the ffmpeg result elsewhere the Graviton machine beats the Intel device by 16%.

And the Graviton is 17% cheaper.

Like, this is a ridiculous canard to even go down. Over half of AWS' new machines are Graviton based, but per your rhetoric they're actually uncompetitive. So I guess no one is using them? Wow, silly Amazon.

I have no connection with them, so I have no idea when these instances will be generally available.

Privileged big customers appear to be already testing them.

The cores designed now by the Arm company for non-embedded applications are distributed into 4 sizes, of which the smaller 2 sizes correspond to what were the original "big and little sizes", but what was originally the big size has been continued into what are now medium-to-small cores, and the last such core before the rebranding was Cortex-A725.

Cortex-X4 is of the second size, medium-to-large. Cortex-X925 was the last big core design before Arm changed the branding this year, so several recent smartphones use Cortex-X925 as the big core, Cortex-X4 as the medium-sized core and Cortex-A725 as the small cores, omitting the smallest Cortex-A520 cores.

Cortex-X4 and Intel Skymont have exactly the same size, 1.7 square millimeter with 1 MB L2 cache memory (in Dimensity 9400 and Lunar Lake). This is about a third of the area of a big core like an Intel P-core and less than a half of the area of a Zen 5 compact core (but AMD uses an older less dense CMOS process; had AMD also used a "3 nm" process the area ratio would not have been so great, and Zen 5 has a double throughput for array operations).

Moreover, Neoverse V3/Cortex-X4 and Intel Skymont/Darkmont have approximately the same number of execution units of each kind in their backends. Only their frontends are very different, which is caused by the different ISAs that must be decoded, Aarch64 vs. x86-64.

The last Arm big core before rebranding, Cortex-X925, was totally unsuitable as a server core, as it had very poor performance per area, having a double area in comparison with Cortex-X4, but a performance greater by only a few tens percent at most. Therefore the performance per socket of a server CPU would have been much lower than that of a Graviton5, had it been implemented with Cortex-X925, due to the much lower number of cores per socket that could have been achieved.

Cortex-X4 was launched in 2023 and it was the big core of the 2024 flagship smartphones, then it has become the medium core of the 2025 flagship smartphones. Its server variant, Neoverse V3, has been launched in 2024 and it has been deployed in products only this year, first by NVIDIA (in Orin) and now by AWS.

It is not at all an obsolete core. As I have said, Intel will have only next year a server CPU with E-cores as good as Cortex-X4. We do not know yet any real numbers about the newly announced Arm cores that have replaced Cortex-A520, Cortex-A725, Cortex-X4 and Cortex-X925, so we do not know if they are really significantly better. The numbers used by Arm in presentations cannot be verified independently and usually when the performance is measured much later in actual products it does not match the optimistic predictions.

The new generation of cores might be measurably better only for computational applications, because they now include matrix execution units, but their first implementation may be not optimal yet, as it happened in the past with the first implementation of SVE, when the new cores had worse energy efficiency than the previous generation (which was corrected by improved implementations later).