Man... what a math class :P thumbs up fur the clarification and enrichment of math culture in the forum ( i mean it! ) :)
Printable View
Man... what a math class :P thumbs up fur the clarification and enrichment of math culture in the forum ( i mean it! ) :)
http://www.chiphell.com/thread-190177-1-1.html
Crap :eek: >30%(ignoring useless Super pi) slower at same clocks with double the cores. I hope these aren't true otherwise I see no reason why anyone in his right mind would buy one.
how come those benchmarks look very similar to results from a PII 920?
from anand bench:
PII 920 gets 3244 pts single
11440 pts multithreaded
an 8 core chip with perf less than something from 2 years ago. lol
Ridiculous scores.
I already posted about it on another forum.
If you look at the chiphell topic ,the OP is confused.He lists the ES which is clearly 6 core by the code,but then posts a screenshot of an 8 core ES from different week and with different revision marker.
Then comes the C10 result of 2340pts for single core,which is on the level of ~2.58Ghz Phenom II.You can see 32bit C10 results here:
http://www.pcstats.com/articleview.c...d=2511&page=10. Scaling of 4.85x is close to 6 core scaling number but CPUz now shows alleged 8 core Zambezi ES.
Similar goes for Super pi in which alleged Zambezi has 12% less performance than 2.8Ghz Phenom II:
http://www.pcstats.com/articleview.c...id=2511&page=8
Lastly ,we have a lowly CPU score from 3dmark06,4900pts,which is a tad lower than what 6 core 1055T gets as can be seen here.Also note that 945 QuadCore Phenom II at 3 Ghz has 14% lower score than this supposed 8 core 2.8Ghz Zambezi. Just ridiculous.
So we have a 10%-30% decrease,according to this "info",when going to Bulldozer.Mind you ,this is almost all fp intensive workload we see and somehow Bulldozer is sucking in it :rolleyes:. We've already seen AMD slide which lists 8 core XX Ghz Zambezi as having around 1.88x the score of 1100T Thuban in C11.5. So we can easily dismiss this whole "test" as either fake one or done on some barely running hardware.
Those results don't look suspicious at all. :rofl:
should be fake ;)
From SA forum,new image:
http://i309.photobucket.com/albums/k...labobby/53.jpg
3dmark06 ~3034pts,lower than Phenom I 9850
C11.5 ~2.86pts, 2.5x lower than 1100T Thuban :p:
Super Pi.... ah who cares anymore lol :D
The chip this Chinese guy has is evidently a seriously borked ES 6 core Zambezi @ 2.6ghz.
PS now the scores are going further down with each new picture,we are in K7 range now^^.This is clearly terrace testing that ES :D
haha:-D Right, this is not possible...2.86 R11.5 with hexacore-rofl...Score as some 2.8 GHz Athlon X3
100 is 25% more than 80.
80 is 20% less than 100.
Much of the confusion here comes in from what the english language leaves implicit. "x%" implies a lot more than it says. In the above statement, "25%" really means "25% of the next number". So "25% more than 80" really means "25% of 80 more than 80". So blame unclear english for the confusion.
More details:
In the english language, the "is" means equals, and the "x more than y" means an operation, or equation. ("5 more than 10 is 15" means "5+10=15")
In the case of "x%", the "%" is like a unit, meaning "divided by 100 (and then multiplied against another number)". (a percentage is also known as "a fraction of 100".) So you divide that "x%" number by 100 to get what the fraction really means in decimal notation. (Decimal notation, not fractions, is the number format in which the rest of this math is done.)
But the "x%" has a secret. It is implicitly tied to the second number in this equation. "25% more than 80" doesn't just mean "0.25 more than 80", it means "25% of 80 more than 80". So once you have the decimal value of the percentage ("decimal value fraction" if you will), you apply it to the second number (using multiplication) to find that percentage of that number. So 25% of 80 is 20, because 0.25*80=20.
Then, the "x% (of y) more than y" means you add ("more") both the original "y" to the value of "x% (of y)" to get the answer to that equation.
"x less than y" also means "subtract x from y", which also means "y minus x", or "y-x", or 80-(25% of 80).
You are wrong.
Look here:
http://blogs.amd.com/work/2010/10/25/the-new-flex-fp/
If we have single threaded fp legacy code,one integer core can schedule instructions on both FMACs.
This means one core can have the whole shared FP resources on its disposal if Core 2 has no fp instructions scheduled in FP scheduler.Quote:
Core 1
2x128b AVX or 2x128b un-recompiled SSE
Oh Jeez... something must be wrong with those scores. =/
Seriously gimbed down Bulldozer ES, AMD doesnt want people know real numbers yet, Intel would panic.
NDA but, you can expect more from bulldozer :up:
Well, duh, if you take cpu on a mature 32nm process its going to clock better than a 45nm one.
Your statement about "rape" is still invalid tho.TDP`s are kept inline only at stock settings.Fact of the matter is phenom X6 aint bad at highly threaded work.
Getting back to core of discussion, BD is going to be build on 32nm with power gating just like sandy.So NOT expecting it to clock better than X6 is not wise.
As for the results, they can pretty much be dismissed.
And no, not because im an AMD fanboy.but if it was that horrible, there would be no point in replacing phenom II with this.
That isn't my intention and I either wasn't clear or you misread me. Most apps aren't well threaded. But those that do scale with cores often benefit more from extra cores than extra clocks/IPC.
My point is simply that what matters to the average user doesn't matter so much to us. The high-throughput multicore case is just as extreme as the high clocks/IPC case. There are plenty of valid desktop uses that utilize many cores - encoding, rendering, heavy multitasking, etc. To determine if BD or SB is right for you will likely come down to using your brain to determine how benchmark scores actually apply to the apps you use and how you use them. There will probably be some cases where SB is the right choice and other cases where BD is the right one.
no, those scores are real. but theres a bug, the cpu always runns @idle, dont mind what cpuz says...
Now that is an interesting piece of information :D
If we assume idle is 800Mhz,as it has always been,and apply 4x (3.2Ghz X8) to C11.5 score of 2.86 ,we arrive to 11.xx score,dangerously close to the score from leaked Donanimhaber slide :D. I dare not to apply 4x to the poor 3dmark06 score or anything else in that picture since it would go through the benchmarking roof :).
And what does running at idle do to it?
that kinda explains the .960v we see
^its stuck at lowest multiplier available, 200x4 = 800mhz