If you want a system that can be a workhorse 128-thred monster on the working days, but reach 4.5GHz boost on the weekends for CS:GO and other video games... you'll want a Threadripper, not an EPYC.
The low clock speeds, and the RDIMMs / LRDIMMs of EPYC add latencies which slow down video game (mostly single-threaded) performance.
--------
For those who don't play video games: there are a variety of single-threaded tasks still in various workplaces. A surprising amount of 3d graphics work remains single-thread bound.
In particular, modeling is typically single-thread bound (the GUI thread, where the user is clicking menus and such). Most custom scripts are single-thread bound, and 3d modelers need a LOT of custom scripts. Those scripters aren't necessarily optimization masters who know how to take advantage of multi-core architectures.
3d Rendering is of course multithreaded. But the 3d artist still needed to click on a lot of menus and scripts to get the mesh to look right.
If you want a system that can be a workhorse 128-thred monster on the working days, but reach 4.5GHz boost on the weekends for CS:GO and other video games... you'll want a Threadripper, not an EPYC.
The low clock speeds, and the RDIMMs / LRDIMMs of EPYC add latencies which slow down video game (mostly single-threaded) performance.
--------
For those who don't play video games: there are a variety of single-threaded tasks still in various workplaces. A surprising amount of 3d graphics work remains single-thread bound.
In particular, modeling is typically single-thread bound (the GUI thread, where the user is clicking menus and such). Most custom scripts are single-thread bound, and 3d modelers need a LOT of custom scripts. Those scripters aren't necessarily optimization masters who know how to take advantage of multi-core architectures.
3d Rendering is of course multithreaded. But the 3d artist still needed to click on a lot of menus and scripts to get the mesh to look right.