AMD Ryzen 3 Linux Benchmarks
openbenchmarking.org
openbenchmarking.org
It outperforms the i7 5960 and it's similarly less than half the price.
AMD can compete well in the enthusiast-on-a-budget segment of the market.
Oh well.
Either way, IMO it's not a roadblock for office and gaming usage.
Besides, mce bug is more critical, since it actually makes the whole system unstable.
On the other hand, the compile thingy has never been an issue yet, despite me compiling a lot of things. (Ryzen 7)
And for gaming, I've never had a game crash, I do doubt that many people really game under Linux yet, most gaming happens on Windows.
Office use is not roadblocked at all.
By the way, for users or Gentoo or other distros which actually build packages when installing them, these segfaults are a very major roadblock for any kind of use case.
There are however reports of segfaults during compilations that seem more Ryzen-specific, though even there GCC versions were said to play a role. It is all a bit obscure currently.
But yeah, AMD is cheaper. And if you compare it to a 5960x at stock 3.3 GHz clock, it is faster.
[1]https://www.eteknix.com/memory-speed-large-impact-ryzen-perf...
There are some minor glitches with the system, but as far as performance on CPU-bound workloads is concerned, I am very, very happy with it. When I look at what comparable chip from Intel would have cost me, I am even happier.
That was a pleasant surprise. The fans Intel ships with its CPUs are ... not very good.
See for example https://stackoverflow.com/a/45201673/149138 and https://stackoverflow.com/questions/43343231/enhanced-rep-mo... - both of which show large performance variance between powersave and performance. In the first example, the CPU clocks down indefinitely to 1.1 GHz from a nominal 2.6 GHz despite being 100% CPU-bound, and performance is cut in half.
Despite having the same governor name, "powersave" with acpi-cpufreq has no relationship. It's using low-frequency software control and generally ramps up to 100% frequency (highest pstate) once CPU-bound code starts running and stays there.
On a similar note, it looks like fab processes are likely hurting AMD with their GPU's. From what I can gather they opted to produce Vega at GloFo's fab on their 14nm proccess, which might explain why they are shipping the air-cooled Vega 64 with a 1.24GHz base clock at a pretty ludicrous 295W TDP.
Ryzen has four ALUs plus four partial vector units. These vector units are all 128 bit. Two can add and two can multiply. An adder and a multiplier can combine to do FMA.
Skylake has four math ports total, all of which can do basic ALU operations. Two of them have 256 bit vector capabilities, and each of those can add or multiply or FMA. A third has limited vector capabilities.
10 core (and higher?) Skylake-X chips upgrade those limited capabilities into an entire new 512-bit vector unit, also capable of FMA.
Depending on your exact needs, Ryzen can be slower or faster than Skylake, but it's usually slower on programs stuffed full of vector math, especially FMA.
I think I got that mostly correct.
Digital Foundry's frame rate and frame time graphs are particularly egregious.