8350rocks
Distinguished
salgado18 :
-Fran- :
jdwii :
IMO its the fairest way in AMD's favor to measure gaming performance as clock rate would be a losing battle with kaby-lake being able to OC to 4.7-5.0Ghz on so many machines.
IPC is the easiest measure when comparing the designs and was often the most common way. Gaming IPC on Ryzen is lower then programs that are more about throughoutput vs latency.
IPC is the easiest measure when comparing the designs and was often the most common way. Gaming IPC on Ryzen is lower then programs that are more about throughoutput vs latency.
We just love to toss the term around when talking about just plain old "performance" when looking at benchmarks and making a huge assumption that IPC is the sole culprit for gains or losses when at the same time we know it is not the CPU alone. Ensue Jackie Chan meme at this point.
The numbers you get from benchmarks have IPC built into them, yes. Is it the most significant measurement? I have absolutely no idea. I would imagine for CB it is, since it might actually implement it's benchmarks around heavy usage of a few selected number of instructions and CPU paths, so the comparisons can be made valid there. Maybe a few other benchmarks keep that consistency across different revisions and versions. I'm pretty damn sure professional benchmarking tools do it when measuring specific things of a *platform*.
You have points of comparison for different numbers, but you can see external influence of the platform affecting those numbers, then *IPC* is not the correct term to use at all. Like palladin said a GOOD while ago, it's a deprecated term from RISC as a unit of measurement. Using it for CISC is weird at best if we are pedantic.
When people doesn't want to compromise on this, Hell breaks loose here. And yes, it is cyclic. Same when refusing to use the "-E" moniker to distinguish from Intel generational CPUs.
Cheers!
IPC was an acceptable measurement up until Ryzen. We talked IPC of Bulldozer and derivatives, Sandy Bridge and derivatives, Jaguar, Conroe, K10 etc. The problem arises when we try to judge the entire performance of a CPU using just this one metric in a multi-threaded, SMT-enabled world.
All reviews show Ryzen going up and down on benchmarks, sometimes faster than Intel, sometimes slower, sometimes a match. Sometimes even the 7700k beats the 6850k. IPC is a good way of measuring the architecture in details, but every program will use resources in a different way, and that became very evident with Ryzen, because the performance is very close to Intel all around (instead of only sometimes, like Bulldozer).
So we could keep discussing IPC to pinpoint strenghts and weaknesses, like strong floating point but weak integer performance, but that can't be used to predict application performance. So, we can't say it's slower than this or that CPU without talking in which program.
All that being said, Ryzen is very competitive and viable against Intel right now. Let's dissect the architecture, but never forgetting how great it is.
Actually, in the old thread I pointed out quite often that IPC as it is used here is inaccurate at best, and lazily ignorant at worst.
Yuka raises a valid point.
IPC in Ryzen is not more than 6% behind Kaby Lake per AMD themselves. AMD know far better than we do what their processor is capable of...I mean...they did design the damned thing after all, right?
Ultimately, performance of the platform as a whole is correct analogy. Platform performance takes into consideration lots of different things, and assuming the architecture is deficient in one area, when it may not truthfully be deficient there is no different than a mechanic telling you that you need to replace the condenser coil in the A/C of your car when you really need to recharge the R-134A coolant.
The issue here is that many do not understand or differentiate the performance, even some of the self proclaimed experts. Were this the case you would see far more discussion about the impact of memory on CCX communication, the implications of the IMC on Ryzen forcing 1T timings on memory, and the fact that Ryzen performs amazingly well in applications that do not require much thread jumping (even exceeding projections in some cases), but significantly worse when the scheduler tends to push threads to a different CCX for various reasons.
All of those factors come into play more significantly on Ryzen than actual IPC. The benchmarks show when a thread is static on a core that it can run with the best that Intel has to offer barring clockspeed deficits.
So, the long answer is noted above, the short answer is that IPC has been used egregiously out of place in most of the discussions about Ryzen. IPC has become a buzzword, and it is inaccurate in 95% of the applications it is used, simply because lots of arm chair engineers do not know a better way to quantify the gaps, or reference the phenomena they see intelligently beyond that buzzword that engineers loathe to see in discussions like this.
Yuka is correct, performance is the correct term, and IPC is tossed around far too casually here and many other places. It annoys me as well, if I am totally honest, and I try to ignore it, but the point stands. He is 100% accurate in this case.