Graviton5 CPU Benchmarks: 30% Geo Mean Improvement Over Graviton4
([Cloud] 4 Hours Ago
5 Comments)
- Reference: 0001645521
- News link: https://www.phoronix.com/review/aws-graviton5
- Source link:
After originally announcing Graviton5 last December, recently AWS finally made the M9g and M9gd instances generally available as the first featuring these new in-house ARM server processors for the EC2 cloud. Graviton5 makes use of Arm Neoverse-V3 cores compared to Neoverse-V2 with Graviton4, support up to 192 cores, and feature a higher 3.3GHz clock speed compared to 2.8GHz on the prior-generation Graviton CPUs. Here is an initial look at how the Graviton5 processor performs over Graviton4.
Graviton5 makes use of the Arm Neoverse-V3 Armv9.2-A cores and offer a 3.3GHz clock speed, 192 cores, larger L3 cache, PCIe Gen6 support, and other enhancements over the Neoverse-V2-based Graviton4 processors that have been available now for two years. Like Graviton4, Graviton5 is still leveraging 12 channel DDR5 system memory but at DDR5-8800 speeds rather than DDR5-5600 with Graviton4.
[1]
Amazon Web Services has promoted Graviton5 with M9g as offering up to 25% better compute performance over the Graviton4-powered M8g instances. AWS also promoted M9g as offering 30% faster performance for databases, up to 35% faster for web applications, and up to 35% for machine learning workloads. Curious about the performance of Graviton5, I've recently been conducting some benchmarks since these new EC2 instances went GA.
[2]
Due to the cost of the testing with AWS not providing any review access, this round of testing is just looking at Graviton4 M8g against Graviton5 M9g. Those wanting more historical Graviton CPU benchmark numbers generationally can see the prior [3]Graviton1 to Graviton4 benchmarks on Phoronix. For those curious how Graviton5 stacks up against AMD EPYC and Intel Xeon in the cloud, those benchmarks will be coming up in a separate article on Phoronix in the coming weeks if there is enough reader interest to justify the cloud costs.
The M8g Graviton4 and M9g Graviton5 benchmarking was done on Ubuntu 26.04 LTS with the Linux 7.0 kernel, GCC 15, and other defaults of that current Ubuntu LTS release. Given that the 16 vCPU size seems to be the undisputed most common instance/VM size across different cloud providers, this M8g and M9g testing was done with the "4xlarge" size providing 16 vCPUs/cores for both Graviton4 and Graviton5. The 4xlarge size pairs the 16 vCPUs with 64GB of RAM.
The m8g.4xlarge was priced on-demand in Ohio art $0.78272 USD per hour. The m8g.4xlarge in the same region was priced at $0.71808 per hour on-demand. Or about a 9% premium opting for Graviton5 rather than Graviton4 at the 4xlarge size.
Let's see what Graviton4 vs. Graviton5 is looking like for CPU performance in the cloud with these completely independent benchmarks.
[1] https://www.phoronix.com/image-viewer.php?id=aws-graviton5&image=aws_graviton5_2_lrg
[2] https://www.phoronix.com/image-viewer.php?id=aws-graviton5&image=aws_graviton5_3_lrg
[3] https://www.phoronix.com/review/aws-graviton-graviton4
Graviton5 makes use of the Arm Neoverse-V3 Armv9.2-A cores and offer a 3.3GHz clock speed, 192 cores, larger L3 cache, PCIe Gen6 support, and other enhancements over the Neoverse-V2-based Graviton4 processors that have been available now for two years. Like Graviton4, Graviton5 is still leveraging 12 channel DDR5 system memory but at DDR5-8800 speeds rather than DDR5-5600 with Graviton4.
[1]
Amazon Web Services has promoted Graviton5 with M9g as offering up to 25% better compute performance over the Graviton4-powered M8g instances. AWS also promoted M9g as offering 30% faster performance for databases, up to 35% faster for web applications, and up to 35% for machine learning workloads. Curious about the performance of Graviton5, I've recently been conducting some benchmarks since these new EC2 instances went GA.
[2]
Due to the cost of the testing with AWS not providing any review access, this round of testing is just looking at Graviton4 M8g against Graviton5 M9g. Those wanting more historical Graviton CPU benchmark numbers generationally can see the prior [3]Graviton1 to Graviton4 benchmarks on Phoronix. For those curious how Graviton5 stacks up against AMD EPYC and Intel Xeon in the cloud, those benchmarks will be coming up in a separate article on Phoronix in the coming weeks if there is enough reader interest to justify the cloud costs.
The M8g Graviton4 and M9g Graviton5 benchmarking was done on Ubuntu 26.04 LTS with the Linux 7.0 kernel, GCC 15, and other defaults of that current Ubuntu LTS release. Given that the 16 vCPU size seems to be the undisputed most common instance/VM size across different cloud providers, this M8g and M9g testing was done with the "4xlarge" size providing 16 vCPUs/cores for both Graviton4 and Graviton5. The 4xlarge size pairs the 16 vCPUs with 64GB of RAM.
The m8g.4xlarge was priced on-demand in Ohio art $0.78272 USD per hour. The m8g.4xlarge in the same region was priced at $0.71808 per hour on-demand. Or about a 9% premium opting for Graviton5 rather than Graviton4 at the 4xlarge size.
Let's see what Graviton4 vs. Graviton5 is looking like for CPU performance in the cloud with these completely independent benchmarks.
[1] https://www.phoronix.com/image-viewer.php?id=aws-graviton5&image=aws_graviton5_2_lrg
[2] https://www.phoronix.com/image-viewer.php?id=aws-graviton5&image=aws_graviton5_3_lrg
[3] https://www.phoronix.com/review/aws-graviton-graviton4