The Stilt
Golden Member
You forgot that GTX 1050 Ti will be locked by no 6 pin connector. It can be bottlenecked by this factor, not the process.
Except the GTX 1050 Ti has a 6-pin connector, since it is a 100W TDP rated card 😉
You forgot that GTX 1050 Ti will be locked by no 6 pin connector. It can be bottlenecked by this factor, not the process.
GB3 for XV correctly reports 0.5x boost clock. GB4 might still use the same code.Last time I checked GB4 doesn't correctly report boost clocks.
Yes it's not there, I searched for all Oct 2 results, not available. Probably a fake from a random user.
Old ST result was 948, so "1061" is not "pretty much what the first leak showed".Looks like all Zeppelin results are gone from DB.
Edit:
For those who speculated that leaked early GB results were done at ~1Ghz:
Old ST result 984pts (@1Ghz?)
New result was 3078pts at presumably full Turbo clock of 2.9Ghz.
3078pts x 1Ghz / 2.9Ghz = 1061pts or pretty much what the first leak showed 🙂.
http://wccftech.com/amd-zen-naples-soc-benchmarks/Old ST result was 948, so "1061" is not "pretty much what the first leak showed".
If the "1Ghz" hypothesis is correct, it means it should be about 15% slower per clock than 6700k. Well, that is actually good. Not good enough to actually brag about it, but good enough to be useful for 3 months before Skylake-X comes out.
Old ST result was 948, so "1061" is not "pretty much what the first leak showed".
If the "1Ghz" hypothesis is correct, it means it should be about 15% slower per clock than 6700k. Well, that is actually good. Not good enough to actually brag about it, but good enough to be useful for 3 months before Skylake-X comes out.
Here is Skylake 6700K vs my 4690K @ 4.2Ghz in 32bit GB3:
http://browser.primatelabs.com/geekbench3/compare/8082269?baseline=8083536
Minor difference in ST, pretty much below 5%.
Are you sure this is at 4.2 Ghz? My i7-6700k at 4.0 Ghz already scores higher than this: http://browser.primatelabs.com/geekbench3/8083540
Division by what? You don't know MT scaling, you don't know SMT scaling and without those, you can't divide.
We know that:You were asked a different question: since you consider the test was indicative of IPC as the appropriate values are one division away, please develop on this further and explain how division is to be applied. Otherwise having people "read up" on what IPC means is hardly helpful for the purpose of this conversation.
It's GB4 result, not GB3.http://wccftech.com/amd-zen-naples-soc-benchmarks/
This is the first score for this SoC, that appeared in the internet.
I used 6200Mhz 6700k scores as reference, rechecking 4800Mhz 6700k with DDR4@3733 leads to same results in points per Ghz.Difference is just 7% and can be attributed to pretty much anything on a platform like this.
My Haswell at 4.2Ghz scores 4060pts, just for reference. At 2.9Ghz it would score around 2800pts.
edit:
As shown above the score fluctuated to 1141pts.
edit2 : the score of 1141 was achieved on 64bit version of GB4 so not directly comparable.
Here is Skylake 6700K vs my 4690K @ 4.2Ghz in 32bit GB3:
http://browser.primatelabs.com/geekbench3/compare/8082269?baseline=8083536
Minor difference in ST, pretty much below 5%.
Your assumption here is beyond rough because you are measuring single core IPC while ignoring the fact that SMT exists. So your IPC value has nothing to do with single thread performance.We know that:
IPC = the average number of instructions executed for each clock cycle. Per processor. Usually it's referred to a single processor core, and that's what I used. But even if you decide to take all instructions executed by all cores, at the end it doesn't change the overall result; see below.
ExecutedInstructions = Time * Frequency * Cores * IPC ; Time in seconds
But we have some fixed values for Frequency (3Ghz) and Cores (8), both for Zen and Broadwell-E.
So we leave them as they are, and only substitute the different values for the two processors:
ExecutedInstructions.Zen = Time.Zen * Frequency * Cores * IPC.Zen
ExecutedInstructions.BDW = Time.BDW * Frequency * Cores * IPC.BDW
Since the application used is exactly the same, as well as the executed job, we can roughly assume that the number of executed instructions is the same in both cases. Here I'm assuming that there's no specific code path for the two processors: only one, the same, is used for both.
So:
ExecutedInstructions = Time.Zen * Frequency * Cores * IPC.Zen
ExecutedInstructions = Time.BDW * Frequency * Cores * IPC.BDW
hence:
Time.Zen * Frequency * Cores * IPC.Zen = Time.BDW * Frequency * Cores * IPC.BDW
Simplifying (read: the infamous division which I talked about is here, applied to the Cores):
Time.Zen * IPC.Zen = Time.BDW * IPC.BDW
But we know that:
Time.BDW = 1.02 * Time.Zen
So:
Time.Zen * IPC.Zen = 1.02 * Time.Zen * IPC.BDW
Simplifying:
IPC.Zen = 1.02 * IPC.BDW
Which is the expected result.
Nevertheless, the queues can receive a maximum of 6 (total) uops per cycle, wheres the schedulers can dispatch 10 of them.The 10 uops cycle probabily is avoid bottlenecks and keep scheduler queues almost empty.
Why?Even if also INTEL has a 6uop cycle from the cache, the shared uop scheduler can be a bottleneck
It might be possible: different microarchitectures have different results depending on the specific task.and so potentially Zen can have greater IPC than intel's in corner cases (and we hope also in more common cases)...
It might be, but actually we have no information.Anyway I am still convinced that Zen will be clocked higher than SKL...
Take a look at the first post of the thread: the Aots ones are there, with some nice chart with processors stick all at 3.2Ghz, making easier the comparison.I remember that Zen was compared to similarly clocked INTEL CPUs in Aots and scored similar... If not, my fault...
I'm not ignoring SMT, because it's part of the calculations.Your assumption here is beyond rough because you are measuring single core IPC while ignoring the fact that SMT exists. So your IPC value has nothing to do with single thread performance.
You have to better read: not absolutely, but roughly the same.Next: your assumption here is even more beyond rough because you consider code executed absolutely the same. When no evidence to this was ever provided.
So this is apparently a GB3 result and it is not in the database. Probably fake.
Difference is just 7% and can be attributed to pretty much anything on a platform like this.
An elaborate hoax then? Too bad. 🙁
Didn't notice the mem scores did you ~ https://browser.primatelabs.com/geekbench3/compare/8082269?baseline=8083540Are you sure this is at 4.2 Ghz? My i7-6700k at 4.0 Ghz already scores higher than this: http://browser.primatelabs.com/geekbench3/8083540
How do you know it is a hoax? All Zeppelin entries are gone. If the score is legit which I think is the case, it matches perfectly with the claims of 40% higher ST IPC over XV core.
Because if you are not making this split then it leads to entire confusion since suddenly a core performance means either single threaded performance (that won't be equal to IPC*clock in your terms), or single core throughput, that will be given by your definition IPC.I'm not ignoring SMT, because it's part of the calculations.
It's you that are talking of different things, splitting the IPC definition in ST & MT, which doesn't make sense.
You have to better read: not absolutely, but roughly the same.
Wait, really. Welp. Even if there are sometimes some interesting things, that ruins it.Please come back with an entry or something substantial and then we talk. It's easy to believe what you want to see. 😉
Edit: LOL, that pic comes from WCCFTech comments section.
Please come back with an entry or something substantial and then we talk. It's easy to believe what you want to see. 😉
Edit: LOL, that pic comes from WCCFTech comments section.
ST score of ~2500pts or so at 3.8Ghz.
At 1Ghz it should score 657pts. 40%more is around 920pts. Leaked Zeppelin scored 984pts at unknown clock. Unknown clock's likelihood of being 1Ghz is 99% now 😉.
99%? Seems too high a likelihood given how much we still don't know...
I would actually agree here with Arach, that we do not know if the CPU in question was running at 1 GHz. It is only our assumption.Well we know the score of XV and we know what AMD publicly stated (multiple)times about ST IPC increase. Add two and two and the leaked scores only make sense if they were done at 1Ghz. If you think they were done at 1.4Ghz then there is zero IPC gain vs XV on a core that has roughly double the resources of its predecessor. Which makes absolutely no sense.
Take your pick 🙂.
Well we know the score of XV and we know what AMD publicly stated (multiple)times about ST IPC increase. Add two and two and the leaked scores only make sense if they were done at 1Ghz. If you think they were done at 1.4Ghz then there is zero IPC gain vs XV on a core that has roughly double the resources of its predecessor. Which makes absolutely no sense.
Take your pick 🙂.