[quotemsg=19247422,0,133194][quotemsg=19247331,0,1282978][quotemsg=19246010,0,133194][quotemsg=19245598,0,25866]check it out:
http://wccftech.com/amd-ashes-ryzen-4-0-ghz-benchmarks/[/quotemsg]
I can do some rough math, but I don't have a 1:1 exact setting match against an Intel CPU with the Titan X on Crazy defaults. The closest I can find is:
http://www.ashesofthesingularity.com/metaverse#/personas/9ea335b6-9477-494f-8aac-190e1ba785e4/match-details/c14a6de6-6451-49c0-a141-51cbfeafec8a
Which has a lower Terrain Shadowing Sample setting [12 Million versus 16 Million], and is on a much newer version of the benchmark. I'll do the math, but it's almost certainly going to bias Intel due to the settings differences. If anyone has an Intel CPU/Titan X or can find a run with similar settings, just post and I'll re-do the results. For now, this should get a *ballpark* estimate. I'll use the average results/CPU Framerate for now.
Performance = IPC * Clock * Number of Cores
5930k: 84.4 = IPC * 3.5 * 12
IPC = 84.4 / 3.5 / 12
IPC = ~2
Ryzen: 70.5 = IPC * 4 * 16
IPC = 70.5 / 4 / 16
IPC = ~1.10
So according to these results [which I stress: BIAS INTEL due to setting difference, Ryzen has 90% lower IPC on this specific benchmark, likely due to core scaling stalling out after a few cores. Even if you factor in the bias in settings, this...isn't great.
What worries me: Remember the benches from late last year? Where I computed sub-Sandy Bridge IPC? Same thing here: Sub Sandy-Bridge IPC again. Yes, the results have bias due to setting differences, and yes, ES sample, but I doubt the differences account to 90%.
If someone has a run with more accurate settings, post and do the math [it's not hard]. Or I'll do it. I'd be VERY interested in a Titan X run, with an Intel CPU, at the same settings. I'm really starting to think we may have aimed high on IPC.
EDIT
I don't want to say something is screwy here, but AMD is using version 1.50 of the benchmark. Most of the results are showing AoS is well past version 2 [2.2 to be precise]. Am I missing something, or is AMD using an ancient version of the benchmark? And the fact they tested at a higher setting then the default for Crazy is odd to say the least. Oh, and I just saw that Half Resolution Terrain was set to off in the Ryzen results, likely dragging performance down a bit, but 90%.
Putting aside the benchmark/version difference: The Ryzen results for IPC are outright CRAP. AMD better hope this isn't indicative of Ryzen performance, otherwise it's DOA.
Calling all Titan X owners: Run the same version of AoS at the same settings. Please. Because something is seriously off here. And i want to know what.
EDIT 2
"Half" resolution terrain, not "High" resolution Terrain. That plus the sample difference are likely dragging AMD's results down. Not sure what to make of this here, as I'm being told by some people 1.50 is a newer version then 2.2. Can anyone please elaborate here?[/quotemsg]
GamerK you can't use AOTS to scale for IPC like that because it's been proven that despite being DX12 and all, it doesn't scale well above 6 cores- so performance on an Intel 6, 8 and 10 core processor is essentially flat.[/quotemsg]
I was JUST going to do a post pointing out that exact fact. So let's do the math assuming scaling drops dead after six cores, shall we?
5930k: 84.4 = IPC * 3.5 * 6
IPC = 84.4 / 3.5 / 6
IPC = ~4.02
Ryzen: 70.5 = IPC * 4 * 6
IPC = 70.5 / 4 / 6
IPC = ~2.93
Which looks a bit better, but is still of 25% from Broadwell. That puts it at about Ivy Bridge IPC. Throw in the different settings, and AMD is likely closer, likely Haswell, which is about what we've been predicting.
The REAL solution is to really divide by total CPU utilization, something like:
Performance = IPC * Clock * Number_Core / Total_CPU_Utilization
Which would account for a CPU that isn't fully loaded. And it handles cases like this better.
Just goes to show how different things look when you have a lot of CPU resources that aren't being used.[/quotemsg]
That is sorted at software level, developers would limit the amount of utilized threads in the coding and AOTS after 4 tends to go nowhere. We are not really testing IPC in that instance, we are testing threading.