US East introductory rate: KVM VPS and CDN origin VPS in our Ashburn region are 50% off, applied automatically at checkout. Explore US East →Monthly and longer billing periods. New orders until 31 October 2026.

← Back to blog

EPYC 9554 vs 9754: Genoa or Bergamo for Your Workload

Maria Ilinca Bostan

In the EPYC 9554 vs 9754 choice, the 9554 (Genoa) gives you 64 full Zen 4 cores per socket at 3.1 GHz base, and the 9754 (Bergamo) gives you 128 Zen 4c cores per socket at 2.25 GHz base. Both run the same instruction set and have 360 W and 256 MB of L3 per socket. Pick the 9554 for per core speed, the 9754 for density.

Because the L3 stays the same size while the core count doubles, the EPYC 9754 works out at 2 MB of L3 per core against 4 MB per core on the EPYC 9554.

Our dual EPYC 9554 and dual EPYC 9754 servers side by side

Both are dual socket builds on the EPYC 9004 platform, with twelve DDR5 memory channels and 128 PCIe 5.0 lanes per socket, two 1 TB NVMe drives and a guaranteed 1 Gbps unmetered port. The processor and the memory sized to it are what differ.

SpecificationDual EPYC 9554Dual EPYC 9754
ArchitectureGenoa, Zen 4Bergamo, Zen 4c
Cores / threads128 / 256256 / 512
Base / boost clock3.1 / 3.75 GHz2.25 / 3.1 GHz
L3 cache256 MB per socket, 4 MB per core256 MB per socket, 2 MB per core
RAM (ECC DDR5)512 GB, 4 GB per core1 TB, 4 GB per core
Price per month€1049€1659
Price per thread€4.10€3.24
Price per core€8.20€6.48
DeliveryBuilt to order, about 14 daysBuilt to order, about 14 days

The 9754 costs €610 a month more and doubles cores, threads and RAM. Per unit it is the better deal, at €3.24 per thread against €4.10 and €1.62 per GB of RAM against €2.05, but only if your workload keeps 512 threads busy. Our breakdown of dedicated server cost per core compares the whole range, Xeon E5 builds included.

Zen 4 vs Zen 4c: what Bergamo actually changes

Zen 4c is not a different architecture. It is the same Zen 4 microarchitecture, laid out more compactly on the silicon so AMD can fit 16 cores on each compute die instead of eight. The instruction set is identical, AVX 512 included. A binary built for the EPYC 9554 runs unchanged on the EPYC 9754, with nothing to recompile and no separate OS image.

Less L3 cache per core

On both chips, cores sit in clusters of eight that share a slice of L3: 32 MB per cluster on Genoa, 16 MB per cluster on Bergamo. The private L2 is 1 MB per core on both. A working set that fits in 32 MB but not in 16 MB stays in cache on the 9554 and spills to main memory on the 9754, which is where the two chips differ most.

Lower clocks inside the same power budget

The compact layout trades frequency headroom for area. The 9754 is rated at 2.25 GHz base and up to 3.1 GHz boost, the 9554 at 3.1 GHz base and up to 3.75 GHz boost. Both are rated at 360 W per socket, so Bergamo shares the same power budget among twice as many cores. How close either chip stays to its boost clock under a sustained all core load depends on the workload.

Memory bandwidth per core

The platform has twelve DDR5 channels per socket for both chips. The 9754 feeds twice as many cores from the same channels, so with the same channels populated each Bergamo core gets half the memory bandwidth of a Genoa core. Total bandwidth depends on how many channels are populated.

When the EPYC 9554 is the better choice

Choose the EPYC 9554 dedicated server when the time to finish one piece of work matters more than how many pieces run at once. Higher clocks and twice the L3 per core help anything that cannot spread across hundreds of threads.

  • Databases. Query execution, index lookups and commits tend to run on a few hot threads, and more L3 per core keeps more hot index pages close to them. Our guide to dedicated database servers covers sizing.
  • Anything with a serial phase or a tight latency target. When one step must finish before the next can start, or a service has a response time target, the slowest path is bound by the speed of one core.
  • Build steps that do not parallelise. Linking a large binary or running a test suite in a single process leaves spare cores idle while one core does the work.
  • Mixed virtualisation where each guest wants a fast core. A hypervisor running Windows desktops, small databases and application servers side by side serves each guest better with fewer, faster cores. See when you need a virtualisation host.
  • Per core licensed software. Half the cores means half the per core licence count.

When the EPYC 9754 is the better choice

Choose the EPYC 9754 dedicated server when your work splits into many independent pieces that each need a modest amount of CPU. The dual 9754 is a 256 core server with 512 threads and 1 TB of RAM in one chassis.

  • Container density. Hundreds of containers that each use a fraction of a core pack cleanly onto 512 threads, and 1 TB of RAM keeps memory from running out first.
  • Many small VMs. Two or four vCPU guests for development, customer sandboxes or per tenant instances. More physical cores lets you give guests their own cores instead of overcommitting.
  • Stateless web or API workers. Throughput scales with the number of workers, so more cores means more requests in flight. Check that your slowest endpoint still meets its target at the lower clock.
  • Parallel CI test shards. A sharded suite finishes when its last shard does, so 256 cores let you run more shards at once. See our page on CI and DevOps servers.
  • Batch rendering or transcoding queues. Jobs are independent, so the queue drains faster with more workers and throughput per euro beats the time of any single job. Our transcoding and media processing guide covers this case.
  • Scale out services consolidated onto one box. A fleet of small servers running one service can often move onto a single machine. Keep a failover plan, because one box is also one failure domain.

A useful test: if adding cores makes the job finish sooner, or lets you run more copies of it, the 9754 gives you more per euro. If one thread is the bottleneck, it does not.

Check per core licensing before you buy 256 cores

Windows Server Standard and Datacenter are licensed per physical core, and every core in the server has to be covered, so a dual 9754 needs licences for 256 cores where a dual 9554 needs 128. Microsoft SQL Server under its per core model and many other commercial databases are counted the same way.

On those products the licence cost for 256 cores can exceed the cost of the server, and the lower price per thread of the 9754 stops mattering. The 9554 or a smaller EPYC is then usually the better total cost. A Linux stack with PostgreSQL, MySQL, nginx or Kubernetes has no per core fee, so density works in your favour. We do not supply software licences, so check your licensing with your vendor before you order.

If neither chip fits your workload

If you want per core speed but 128 cores is more than you need, the dual EPYC 9254 costs €739 a month for 48 cores and 96 threads at 2.9 GHz base and up to 4.15 GHz boost, with 256 GB of DDR5. It uses full Zen 4 cores with 128 MB of L3 per socket, and for per core licensed software it means licences for 48 cores instead of 128.

Every dual socket server has at least two NUMA nodes, one per socket, and memory attached to one socket takes longer to reach from the other. Software that keeps its threads and memory on one socket avoids that penalty, and lscpu and numactl show you the layout. Our post on single vs dual socket servers and NUMA explains when the second socket helps and when it gets in the way.

Questions we get

Do I need to recompile software for the EPYC 9754?

No. Zen 4c runs the same instruction set as Zen 4, including AVX 512. Binaries, container images and OS images built for the EPYC 9554 run unchanged on the EPYC 9754.

Is the EPYC 9754 faster than the EPYC 9554?

Per core, no. The 9554 clocks higher and has twice the L3 per core. Per server, the 9754 has twice the cores, so on work that scales across all 512 threads it can get more done in total. Which one finishes your job first depends on how well the job parallelises, so test your own workload.

Why does the EPYC 9754 server come with 1 TB of RAM?

Both servers are sized at 4 GB of RAM per core, so doubling the cores doubles the memory. If you need a different amount, ask support before ordering and we will quote it for that server.

How long does delivery take?

Both are built to order with a delivery estimate of about 14 days. There is no setup fee, and faster guaranteed ports than the included 1 Gbps can be added at checkout for a monthly fee.

Genoa vs Bergamo: order for your bottleneck

If single thread speed or a per core licence count is your constraint, start with the dual EPYC 9554 at €1049 a month. If the number of things running at once is your constraint, the dual EPYC 9754 at €1659 a month gives you 256 cores and 1 TB of RAM. Both are offered in all 11 of our dedicated server countries at the same price, and you can compare them with the rest of the range on our dedicated servers page.

Ready in under a minute

Deploy your first server now.

No contracts, no minimum term. Start on an Ion KVM VPS at €0.0063 an hour and move to a monthly bare-metal server the day you outgrow it.

$ curl https://my.voxa.host/api/v1/products -H "Authorization: Bearer fbk_…"

KVM VPS billed hourly, capped monthly · Dedicated billed monthly · No setup fee

Included on every plan
Free IPv4
Every VPS
Unmetered traffic
Every plan
DDoS protection
1 Tbps · L3/L4
Root access
Included
Setup fee
€0.00
Minimum term
None