The stuff Hacker News actually recommends.

GPUs and CPUs

AMD Ryzen vs AMD Threadripper

Hacker News owners slightly favor the AMD Ryzen.

AMD RyzenAMD Threadripper
Owners with an opinion35572
Positive verdicts77% of 26576% of 45
Positive/negative since 2024109/2411/5
Happy after 3+ years51
Longest happy owner7 yrs7 yrs
Praised forperformance and reliabilityperformance and reliability
Criticized fornoisevalue
Newest comment

Updated

What owners wrote about both

AMD Ryzen: Recommends itAMD Threadripper: Likes it
That's awesome re the Threadripper Pro! Yes, DCS World in particular, but also Star Citizen (where nothing else comes close at the moment) and to some degree iRacing. It went from stuttering all the time (bad 99% lows) on a well overclocked (all core 4.4ghz) 3900XT to butter smooth frame rates in DCS - and that's including custom scripts I had to exclude before (Streamdeck integration, etc). I can now push DCS World to three screens; even on my lowly (for the task) 3070, the lowish 30-40-50 depending on weather FPS numbers combined with Free(G)sync monitors are never stuttering so it still feels smooth. I attribute it to the CPU never being the weak link; also, have reasonably good memory (4x 16GB C16-3600 Neos at XMP/3600mhz). For gaming, there's no better value for money right now than the 5800X3D - if you already have an AMD system. And even then, if not, and you're not made of money.
AMD Ryzen: Likes itAMD Threadripper: Recommends it
> Wonder what would people suggest if one is looking into a long-term many-core Linux workstation setup as of today? Well, ryzen 5000-family and threadripper 3000-family core count do not intersect(16v24). if you need more than 16 cores and dont mind spending twice as much per core, go with threadripper. otherwise, ryzen 5950x is an absolute beast when cooled properly and is only $480
Switched from the AMD Ryzen to the AMD ThreadripperAMD Threadripper: Likes it
One reason I chose to buy the lowest-end Threadripper instead of the highest end Ryzen. In the future, even if there's never any compatibility with socket sTR5, the parts in the same generation provide a part-by-part upgrade path up to 96 cores, 1TB of RAM (or was it 2TB? I forget), and 128 PCIe lanes.
AMD Ryzen: Likes itAMD Threadripper: Likes it
We use pytest with xdist and we run as many as the system it is running on can handle. On my threadripper machine with 256GB I could run about 60 concurrent tests, on my 9955hx machine I use day to day I can run 13. On a MBP I think it's about 8-16. There is diminishing returns with more processes. Each xdist process gets it's own testdb. If I was designing it from scratch I would use a single testdb and point all the python processes at it, and never clean up between tests or even between test runs. This is both faster and a better test, as I feel that clearing the db makes it very hard to detect overly broad queries unless you go out of your way to pack in a lot of extra harness data which people almost never do and is a chore.
AMD Ryzen: Likes itAMD Threadripper: Likes it
Beelink GTR9 Pro. It has dual 10G Ethernet interfaces. And get the 128GB RAM version, the RAM is not upgradeable. It isn't quite shipping yet, though. The absolute best would be a 9005 series Threadripper, but you will easily be pushing $10K+. The mainstream champ is the 9950X but despite being technically a mobile SOC the 395 gets you 90% of the real world performance of a 9950X in a much smaller and power efficient computer: https://www.phoronix.com/review/amd-ryzen-ai-max-arrow-lake/...
AMD Ryzen: NeutralAMD Threadripper: Neutral
I would use ECC memory if I could. I used to use a TR 2920x with ECC but now I'm on a Ryzen 7950x with non-ECC. Unbuffered ECC memory is the only one supported by Ryzen, and it's slower or more expensive or both compared to the equivalent-capacity non-ECC memory. The latest Threadripper lineup supports Registered ECC, but Threadripper is overkill (cost, threads, PCIe lanes) for home users like myself.
AMD Ryzen: Likes itAMD Threadripper: Likes it
While at equal clock frequency the Intel CPUs are a little faster in single-thread applications, their main weakness is that at equal power consumption their clock frequencies are much lower in multi-threaded applications, which leads to much lower multi-threaded performance. This can be easily noticed when comparing the base clock frequencies, which are more or less proportional with the actual clock frequencies that will be reached in multi-threaded applications. For instance a 7950X has 4.5 GHz versus the 3.2 GHz of 14900K. Similar differences are between Epyc and Xeon and between Threadripper and Xeon W. In desktop CPUs Intel can hide their very poor multi-threaded performance by allowing a much higher power consumption. However this method does not work for server and workstation CPUs, because these already have the highest TDP that is possible with the current cooling solutions, so in servers and workstations the bad Intel MT performance is much more visible. Intel hopes that this will change in 2024, when they will launch server and workstation CPUs made with the new Intel 3 CMOS process. In the absence of actual benchmarks, a good proxy for the multi-threaded performance of a CPU is the product between the base clock frequency and the number of cores. For Intel hybrid CPUs, an E-core should be counted as 0.6 cores. For example a Threadripper 7960X should be expected to be (24 cores x 4.2 GHz) / (16 cores x 4.5 GHz) = 1.4 times faster than a 7950X in multi-threaded app…
AMD Ryzen: Likes itAMD Threadripper: Likes it
>which is insecure Splitting IOMMU groups is not inherently insecure; doing so without ACS is insecure. It is true that's not the motherboard vendors fault - it is because Intel designed it that way. ACS (the part of PCIe which makes sane IOMMU group splitting possible) works great on my Zen products (Ryzen, Threadripper, EPYC, etc.) It also works fine on my Intel Xeon products. Intel client silicon is the odd man out here, and if you ask me that's hardly an accident. It falls neatly in line w/ their other artificial market segmentation. (They do the exact same thing w/ ECC RAM.) I'm mostly just jaded because my use-case (PCIe passthrough for a 'gaming VM') is hardly conducive to enterprise grade hardware (Xeon SKUs w/ low base clocks, headless GPUs designed for compute, etc.) yet vendors like NVidia and Intel choose to make this use-case difficult/impossible to implement on their consumer grade offerings. It gets old after a while. I, for one, am really glad AMD shook things up in this regard in the CPU space.