First of all, noob cool down. I am not planning to put you down in this forum in anyway, and that is not my intention. Let's have a discussion, not an argument.
Secondly, lets make somethings clear. When I say 'IPC', I mean the ratios of the IPC's for a given task (although IPG like you said would be a much better term to call it), and that's why all my comparisons
are in terms of IPG ratios. Like you must already know, percentages are nothing but ratios expressed with 100 as the base.
Even though I shall use IPG from now on, its still an inappropriate term, as no mordern chip does around 60 instructions per GHz. However, I hope we both understand what kind of performance relative measurement IPG* is for us, and I'll base further discussions using this (hopefully) mutually understood term.
Also, we are NOT dealing with proper scientific data here, and hence minor variations are definately bound to occur. Scientifically speaking, a 5% variance is well tolerated for most rough measurements (although I prefer values that are within 3%).
Now let me go through the points you've put through, and try to counter them.
so at turbo speeds, 238/4.0=59.8 per ghz for the 4300, and 240.7/4.0 = 60.7 for the 8320, and 252.1/4.2 = 60.2
That would mean that the 8320 is the best AMD cpu because its IPC is higher ... This is why you can't assume turbo speeds = actual speed.
Avg IPG for FX chips, for that task = 180.7/3 = 60.23.
Therefore, would you still claim the 8320 to have best IPG*?? Hell no, its not even 0.8% above the mean value!!
A more rational understanding is that all FX chips have the same IPG, as they all come with a 1% tolerance value. The slight variations are more than acceptable margins of error in our expirement.
the ratio of 80 to 60 is 33, not 37
The ratio isn't 33, its the
percentage speed increase that is.
Again, my ratio = 1.37. Your ratio= 1.33.
Whats the % difference? (137/133)x100= 1.03%. My value was only 3% faster than yours, again which very comfortably sits within the margin or error.
274.9 for the 2500k at 3.7 turbo =74
so now you lost that arguement even deeper (74/60 = 1.23, in other words 23% not 51%, you just lost 55% of your lead) instead compare it to Ivy bridge since its faster than SB.
No I didn't
![Smile :) :)](/data/assets/smilies/smile.gif)
Again you missed a very crucial point. These IPG* values of 74 and 60 which you are using here, are for an
entirely different workload. These are for cinebench, NOT AAC encoding. As I'm sure you already know, IPG ratios of AMD vs Intel vary from task to task, based on the strengths and weakness of each architecture, for the particular task in concern. There is no fixed value that suits all the tasks.
For cinebench I calculated the intel/amd ratios as 1.37(37% faster), and for AAC encoding 1.50(50 % faster).
Again, note that if I used IB instead of SB for that AAC test calculations, the results would have been even more towards Intel's favour, and yes, exceeding 50% perhaps!!
Please run your own calculations for single threaded
AAC encoding, and tell me what numbers you arrive at.
I shall be waiting for your calculation results.
if said program scales 100%, then IPC for said program = single core IPC X speed X cores.
Perfectly correct, but IPG ratio measurements get so much more simplified if we just consider single cores at identical frequency.
don't think i have ever seen ht boost even close to 30%
Regarding HT giving upto 30% more performance, I possibly am wrong. My mistake.
scaling of 102% How can you scale over 100%
2%, once more, well within error tolerance limits. Rounding of data values are main contributers to this kind of error.
"After all, if its the 50% that you claim, this should never happen:"
Ofcouse it won't!! You took the wrong ratio. Take 37% and see what it comes upto. It'll be closer to real life, but you'd still be off. Why? Because, your method of calculation is also flawed. Workloads scale differently among multiple cores on AMD and Intel chips. Have you considered that into your calulations?
This is the reason I stick to single threaded calculations.
![Smile :) :)](/data/assets/smilies/smile.gif)