Would it make any sense, to upgrade Ryzen 1600 to 2600 (2nd-gen)?

[sdifox]

No. Wait for zen 2.

 

[bfun_x1]

3.8GHz on all core for a Zen1 non-X CPU is pretty good for h24 ! Didn't you try to overclock the 2600X ? However the perfomance gap with a 3600X will clearly be bigger.

I did try to OC the 2600X and it went just like everyone said it would. Lots of voltage and heat for very little gain. I think I was struggling with 4.1 and that's not really an improvement over the stock 4.0/4.2.

If the rumors of a 5GHz 3700X are true I might have to choose that over a 3600X. It's not like I need more cores but 5GHz is 5GHz.

 

[Justinbaileyman]

I'm with everyone else here Larry, you should just hold off a couple of months for the next gen cpu's and maybe new motherboard if need be. There would be very little gains for the extra money you'd be spending right now vs just waiting a tad bit longer.

 

[bfun_x1]

It's weird, I just updated the firmware on my Ryzen R5 1600 rig, and as part of that, I reset to UEFI defaults, reboot, flash UEFI, allow it to reboot itself twice, enter UEFI, reset to defaults (new defaults, if any), reboot, enter UEFI, set XMP and RAM speed, reboot, optionally, enter UEFI and set overclock, reboot, and allow it to boot into Windows 10.

Well, I chose not to overclock it this time, and it seems... snappier? I don't quite understand it. Something about manual overclocking, seems to muck something up, regarding latencies somehow. Or maybe, it has something to do with the power plan, interacting with the scheduler, and whatnot, when manually overclocking. I don't know. Sure, some benchmarks are higher overclocked, but ... I like "snappy".

There were a couple of times where my 1600 dropped down to 2.0 on all cores when I was trying to overclock it. I don't know why it happened. I assumed it was a bug somewhere. I didn't even notice it happened until I benchmarked it. The BIOS was correct but the software was reporting 2.0.

 

[VirtualLarry]

There were a couple of times where my 1600 dropped down to 2.0 on all cores when I was trying to overclock it. I don't know why it happened. I assumed it was a bug somewhere. I didn't even notice it happened until I benchmarked it. The BIOS was correct but the software was reporting 2.0.

I encountered something similar, when pushing for 4.0Ghz, especially with earlier BIOSes. Seemed to be semi-common, I read about other people with similar issues too, close to or at the 4.0Ghz mark on Ryzen 1st-gen CPUs.