The Ryzen 5950X CPU and Noctua NH-D15 cooler arrived yesterday already. So while I wait for the memory (to arrive tomorrow), I decided to install the processor under the stock cooler for the old Ryzen 1700 — just to check that the new CPU works, run some tests and upgrade to Windows 11. As the installation of the NH-D15 is a more complex affair, and with the big size of it covering up the memory, I decided to wait to install it until the memory arrives, so that I don't have to redo anything.
However, this simple CPU swap almost ended in disaster for the old CPU, as it was firmly cemented to the heat sink. Even though I was aware of the potential issue, and tried to apply some gentle rotational force, the whole thing was firmly stuck until it suddenly came loose, ripping the CPU out of the socket. Luckily, the CPU stayed fixed to the cooler without falling off, and without any pins visibly bent. I was ably to pry the cooler and CPU apart with a flat headed screwdriver. I will have to look for a better technique next time. By the way, it is good that AM5 has a new socket design that will not have this issue.
Installation of the 5950X was easy though, and I am happy to say it works and runs fine. However, as expected under this small cooler, it gets into the thermal limits very quickly when I give it something to do. At idle in Windows it runs at ~54° C with the CPU fan at ~1700 rpm, which is OK but noticeably more audible than with the Ryzen 1700, and if I start a sizable software build, it ramps steeply up to 90° C with the fan at an awfully noisy ~2800 rpm. Hopefully, the Noctua NH-D15 will do much better. It has to be said that I have no case fans running in my Antec Sonata III case. I have had the single rear fan disconnected, and I even put in some improvised cardboard for further sound dampening. I will have to revisit that solution and finally connect the case fan, I think, as to give the case some airflow.
As regards early performance results, I tested building all 112 library configurations of
OWLNext 7.0 with the Microsoft Visual Studio 2022 toolset. Using the parallel build option, this job took 167 seconds, versus 390 seconds with the Ryzen 1700 — that's a 134% speed-up (or 57% less waiting, if you prefer). Not bad! With proper cooling, I guess the new processor will do even better. Also note that, although configurations were built in parallel (at a maximum of 16 configurations at a time), this test was performed with each configuration being built without using multi-threading. This limitation is due to memory constraints. When I get more memory, I should be able to allow the toolset to use multi-threading, which should give me another speed boost. The Ryzen 1700 saw a ~15% speed increase when going from single-threaded to multi-threaded compilation in this test (with a maximum of 8 configurations at a time), although it was working at the limits of available memory and sometimes running out of heap space.
My plan to upgrade to Windows 11 ran into an apparently unsurmountable problem, though: My olden Radeon R7 250 GPU does not support UEFI, which prevents the motherboard from turning on support for Secure Boot, a feature required by Windows 11. I may have to upgrade to a modern GPU. Let me know if you have any advice. Perhaps I will just stick with Windows 10 on this PC. Perhaps I will just do a reinstall to freshen things up a little (login has started to take a very long time for some strange reason — the problem shows up in the Windows logs, but I have found no obvious cause and solution).
No love for Bristol Ridge in the poll?!
Sorry, that poor chip is easy to overlook in the shadow of the "Zen" launch. That said, it was a useful pioneer on the AM4 platform, I guess. So for those early adopters who started out on AM4 with this chip and since upgraded, you can vote as if you had "Zen", if you want. Again, the point of the poll is to get a feel for how many used the opportunity to do a CPU upgrade across generations on the AM4 platform.