
AMD EPYC 9575F
Expert rating8.9 / 10
- Brand:
- AMD
- Form Factor:
- Server & Enthusiast
- CPU Socket:
- SP5
- Core/Thread Count:
- 64C/128T
- TDP:
- 400W
- iGPU:
- None
- CPU Series:
- EPYC
Consumercarts is reader-supported. Learn more
Disclaimer: The price and specification of the given product may differ from the actual product. Please confirm on the retailer's website before buying.
Manufacturer: AMD Last updated: 2026-10-10
AMD EPYC 9575F Review
AMD EPYC 9575F 64-core 128-thread SP5 server processor, 3.35GHz base / 5.0GHz boost, 400W TDP, 320MB L3 cache, Zen 5 "Turin"
The EPYC 9575F is a frequency-optimized EPYC processor built for per-core licensed software (databases, EDA tools) where clock speed matters more than raw core count. Built on Zen 5 "Turin" and rated for 400W, it pairs 64 cores and 128 threads with a 3.35GHz base clock that boosts up to 5.0GHz, backed by 320MB of L3 cache on AMD's SP5 server platform.
Core Count and Workload Fit
With 64 cores and 128 threads, the EPYC 9575F is built for data center workloads that scale across many cores: virtualization hosts, container orchestration, databases, and web-tier fleets. Base clock of 3.35GHz with boost to 5.0GHz means per-thread performance is a priority for this SKU, not an afterthought. The 320MB L3 cache keeps per-core cache allocation reasonable for the socket.
Platform, Memory, and Cooling
The EPYC 9575F runs on AMD's SP5 platform with 12-channel DDR5 memory support and up to 128 PCIe 5.0 lanes per socket, giving it enormous memory bandwidth and I/O headroom for NVMe storage arrays and high-speed networking. It supports both single-socket (1P) and dual-socket (2P) server designs, giving system builders flexibility on scale. At 400W, it requires server-grade cooling: high-static-pressure fans and a chassis designed for sustained data-center airflow, not a repurposed desktop tower.
Comparison to Alternatives
Against a core-dense EPYC SKU like the EPYC 9654 in this catalog, the EPYC 9575F gives up core count for meaningfully higher clocks, which matters directly for per-core-licensed database and EDA software where license cost scales with cores, not threads. Compared to Intel Xeon W workstation parts in this catalog, it adds genuine dual-socket server scalability and far more memory channels. It is the right EPYC pick when licensing costs favor fewer, faster cores over many slower ones.
Our verdict
Reviewed by Burooj Alam. Rated by us, not by users.
Expert rating8.9 / 10
The EPYC 9575F is the right call when per-core software licensing makes clock speed worth more than core count.
Best for
- Per-core licensed databases (Oracle, SQL Server)
- EDA tools billed per core
- Latency-sensitive server workloads
Not for
- Massively parallel batch jobs
- Cost-per-core-sensitive deployments
- Workloads that scale linearly with cores
Specifications
What these specs meanCores and threads
| Core Count | 64 cores |
|---|---|
| Thread Count | 128 threads |
| Core Architecture | Zen 5 "Turin" |
Clocks
| Base Clock | 3.35 GHz |
|---|---|
| Boost Clock | 5.0 GHz |
Cache
| L3 Cache | 320 MB |
|---|
Platform
| Socket | SP5 |
|---|---|
| Multi-Socket Support | 1P/2P |
Memory
| Memory Channels | 12 channels |
|---|---|
| ECC Support | Yes |
Power and thermals
| TDP | 400 W |
|---|
Measured results
SPEC CPU 2017
Best published result on spec.org as of 23 Sept 2026.
| SPECrate® 2017 Integer (base) | 881 |
Cores 64 · Tested in ASUS RS520QA-E13-RS8U (3.30 GHz, AMD EPYC 9575F) · Published by ASUSTeK Computer Inc., Sep-2025
Full disclosure on spec.org| SPECrate® 2017 Floating Point (base) | 915 |
Cores 64 · Tested in ASUS RS520QA-E13-RS8U (3.30 GHz, AMD EPYC 9575F) · Published by ASUSTeK Computer Inc., Sep-2025
Full disclosure on spec.org| SPECrate® 2017 Integer (base) | 1,760 |
Cores 128 · Tested in ASUS RS720A-E13-RS8U (3.30 GHz, AMD EPYC 9575F) · Published by ASUSTeK Computer Inc., Jul-2025
Full disclosure on spec.org| SPECrate® 2017 Floating Point (base) | 1,830 |
Cores 128 · Tested in ASUS RS720A-E13-RS8U (3.30 GHz, AMD EPYC 9575F) · Published by ASUSTeK Computer Inc., Jul-2025
Full disclosure on spec.orgSPEC®, SPECrate® and SPECspeed® are registered trademarks of the Standard Performance Evaluation Corporation. Copied by permission of the Standard Performance Evaluation Corporation (SPEC). Results retrieved from www.spec.org on 23 Sept 2026.
Measured results
SPEC CPU 2026
| SPECrate® 2026 Floating Point (base) | 364 | 1-chip system · CloudDC A+ Server AS -1116CS-TN (H14SHM , AMD EPYC 9575F). Licensee: Supermicro. Published May-2026. · Source |
| SPECrate® 2026 Floating Point (base) | 778 | 2-chip system · QR8218-D3 (AMD EPYC 9575F). Licensee: Maginfra Co., Ltd. Published Sep-2026. · Source |
| SPECrate® 2026 Integer (base) | 317 | 1-chip system · CloudDC A+ Server AS -1116CS-TN (H14SHM , AMD EPYC 9575F). Licensee: Supermicro. Published May-2026. · Source |
| SPECrate® 2026 Integer (base) | 697 | 2-chip system · QR8228-D3 (AMD EPYC 9575F). Licensee: Maginfra Co., Ltd. Published Aug-2026. · Source |
Best published base result for this chip count at www.spec.org as of 23 Sep 2026. SPEC CPU 2026 scores are not comparable with SPEC CPU 2017 scores.
Retrieved 23 Sept 2026
SPEC®, SPECrate® and SPEC CPU® are registered trademarks of the Standard Performance Evaluation Corporation. Copied by permission of the Standard Performance Evaluation Corporation (SPEC). Results retrieved from www.spec.org on 23 Sep 2026. More information: www.spec.org/cpu2026/
FAQs
What are the key specifications of the AMD EPYC 9575F?
The AMD EPYC 9575F has 64 cores and 128 threads, a 3.35 GHz base and 5.0 GHz boost clock, 320 MB of L3 cache and a 400 W TDP. Socket: SP5.
Will the AMD EPYC 9575F work with my current setup?
The AMD EPYC 9575F lists Socket is SP5. Check that against the hardware you already own before buying, since this is the field that most often decides whether a part fits.
Who is the AMD EPYC 9575F best suited to?
Best suited to: Per-core licensed databases (Oracle, SQL Server); EDA tools billed per core; Latency-sensitive server workloads.
What are the drawbacks of the AMD EPYC 9575F?
Not the best fit for: Massively parallel batch jobs; Cost-per-core-sensitive deployments; Workloads that scale linearly with cores.
