Host compute

CPU Catalog

A starter comparison of CPUs that matter for AI systems, from conventional server sockets to custom Arm and unified-memory designs.

How to read this table

CPU comparison is tricky because sockets, instances, boost behavior, memory population, and compiler/runtime maturity all matter.

This table tracks platform orientation and public headline specs; detailed benchmarking should live in separate posts.

Metric Xeon 6EPYC 9005Grace CPU SuperchipAxionGraviton4M4 Max
Vendor IntelAMDNVIDIAGoogleAmazonApple
Family Xeon 6 P-core and E-core families5th Gen EPYC TurinGraceGoogle Cloud AxionAWS GravitonApple Silicon M-series
ISA / core x86-64; Granite Rapids P-cores and Sierra Forest E-coresx86-64; Zen 5 and Zen 5cArm Neoverse V2Arm Neoverse V2Arm Neoverse V2Arm-based Apple CPU cores
Core count Up to 128 P-cores or up to 288 E-cores by platform classUp to 192 cores / 384 threads144 Arm cores in Grace CPU SuperchipInstance-visible core counts vary by Google Cloud machine type96 cores per processor classUp to 16 CPU cores
Memory system DDR5 and MRDIMM platform options12 channels DDR5; large socket memory capacityUp to 960 GB LPDDR5X ECCDDR5 cloud server platformDDR5 cloud server platformUnified LPDDR memory, up to 128 GB
Bandwidth notes Intel positions Xeon 6 around higher memory bandwidth and I/O versus prior Xeon generationsDDR5-6400 class platform bandwidth with 12 memory channelsUp to 1 TB/s class aggregate memory bandwidth depending on module configurationGoogle emphasizes performance and efficiency versus comparable x86 and Arm cloud instancesAWS positions Graviton4 with higher memory bandwidth than Graviton3Up to 546 GB/s unified memory bandwidth
Target role General server, cloud, HPC, networking, and edgeGeneral server, cloud, HPC, database, and AI host CPUHPC and AI host CPU paired with NVIDIA accelerator platformsGeneral-purpose cloud workloads and CPU-side AI infrastructureEC2 general-purpose, memory-optimized, and scale-out cloud workloadsWorkstation-class client compute and local model experimentation
Notes Track P-core and E-core families separately for benchmark work.Strong baseline for high core-count x86 host compute.Interesting because memory bandwidth and energy efficiency are first-class design points.Public die-level details are sparse, so track by cloud instance family.Most useful to compare through EC2 instance families rather than bare chip SKUs.Not a server CPU, but useful for unified-memory local LLM and media workloads.
Sources