In databases you pay per core
Commercial database engines — Oracle Database Enterprise Edition and Microsoft SQL Server Enterprise — are licensed per physical core. Licensing cost quickly exceeds the cost of the hardware itself: a single Oracle EE license runs into tens of thousands of dollars per core. With that economics, the overriding goal of CPU selection is the fewest possible cores at the highest possible per-core performance.
billed per core
more than the server
licensing threshold
The density trap: for per-core databases a 128-core CPU (e.g. EPYC 9755) would mean enormous licensing costs. Here we invert the logic — we pick a chip with few, very fast cores.
AMD EPYC 9175F (Turin, Zen 5)
The 9175F is a specialised "F" (high-frequency) model in the EPYC 9005 "Turin" family. Its unique design — 16 cores spread across many chiplets (CCDs) — gives each core access to a huge pool of L3 cache, which is ideal for databases.
| Parameter | AMD EPYC 9175F |
|---|---|
| Architecture | Zen 5 (Turin), socket SP5 |
| Cores / threads | 16 / 32 |
| Clock (base / boost) | 4.2 GHz / up to 5.0 GHz |
| L3 cache | 512 MB (32 MB per core) |
| Memory | 12-channel DDR5-6000 |
| PCIe | 128 lanes PCIe Gen5 |
| Socket configuration | 1 or 2 sockets (2P platform) |
| TDP | 320 W |
Cache is the key: 512 MB of L3 across just 16 cores gives 32 MB of cache per core — many times more than typical high-density CPUs. For databases this means fewer memory accesses and higher query performance.
The socket also supports 2 CPUs: the SP5 platform lets you fit two 9175F processors in a single server, doubling database compute — a combined 32 high-frequency cores (and the same number of licensed Oracle EE / MS SQL EE cores). An option for larger databases that need more cores while keeping maximum per-core performance.
Fewer cores = lower licensing cost
Since Oracle EE and MS SQL EE charge per active physical core, the 16-core 9175F minimises the number of licenses — while high clocks and a huge cache make those few cores exceptionally productive. You pay for fewer cores and get more real performance from each.
- 16 cores = a low, predictable Oracle EE / MSSQL EE licensing threshold
- High per-core performance reduces the need to buy additional licenses
- License savings often dwarf the CPU price difference many times over
- In Proxmox VE the database is isolated on a dedicated VM with pinned vCPUs
In mixed environments we use a hybrid approach: the dense EPYC 9755 for general applications and virtualisation, and the high-frequency EPYC 9175F for per-core-licensed databases — each workload on the right hardware.
Per-core performance: cache & clocks
Databases are highly sensitive to latency and single-thread performance. Three traits of the 9175F meet perfectly here: huge cache, high clocks and wide memory.
512 MB L3 cache
More "hot" data fits in the CPU cache, reducing costly trips to RAM. Buffers, indexes and query plans stay closer to the core.
Clocks up to 5.0 GHz
High clocks accelerate single-threaded operations and short OLTP transactions — where the time of an individual query matters, not just parallelism.
DDR5 + PCIe Gen5 NVMe
12-channel memory and fast NVMe Gen5 drives provide high I/O throughput — critical for transaction logs, tempdb and large scans.
The result: the same (often higher) database performance with fewer licensed cores than on older, slower CPUs.
Also excellent for PostgreSQL and MySQL/MariaDB
The 9175F's strengths aren't limited to commercial databases. Open-source engines — PostgreSQL, MySQL and MariaDB — also benefit greatly from high clocks and a large cache, even though they carry no per-core fees.
- PostgreSQL: faster query plans, shorter transactions, efficient VACUUM and indexing
- MySQL / MariaDB: high OLTP performance and fast InnoDB buffer operations
- Fewer, higher-performance cores simplify tuning and cut hosting costs
- Full isolation and HA in Proxmox VE — replication, PBS backup, cluster failover
For open-source databases the 9175F is simply a very fast "quiet hero" of performance — no licensing compromises, with the full benefit of cache and clocks.
Consolidation recommendation: databases that don't require per-core licensing — such as MySQL/MariaDB and PostgreSQL — are best placed on the dense EPYC 9755. That way the valuable, high-frequency 9175F cores are reserved exclusively for per-core-licensed databases (Oracle EE, MS SQL EE), without burdening the cores the client pays for per licensed core. Free open-source engines then leverage the 9755's high core count, while the licensing budget stays minimal.
9175F vs 9755 — recommendation
Both CPUs come from the same Turin family but answer different needs. The choice depends on the workload profile and licensing model.
| Criterion | EPYC 9175F | EPYC 9755 |
|---|---|---|
| Profile | Databases, per-core | General apps, consolidation |
| Cores | 16 (high clocks) | 128 (density) |
| Cache per core | 32 MB | 4 MB |
| Optimises | DB license cost | Host count / OPEX |
Our recommendation: for Oracle EE / MS SQL EE servers — the EPYC 9175F. For general virtualisation and consolidation — the EPYC 9755. In larger environments we combine both, matching the hardware to each workload.
We'll match the hardware to your databases
We'll help estimate the number of licensed cores and pick a CPU that minimises Oracle / MS SQL license costs — while keeping full database performance.
⚡ Free consultation → EPYC 9755 for applications