keithlm :
AH... but you are conveniently forgetting that is not just a stepping... there is also a new die. Are you going to pretend that the last time they did a stepping and die together that nothing changed? Is that your final prediction?
Because you are the almighty Chad Bogas we must accept your predictions as being more important than anybody else's predictions. Good luck with that one. Especially since you already failed.
Keith,
Even though you should be a master of recognising failure on a daily basis(I presume you have a mirror), what have I supposedly failed at?
I am stating that the per core performance of Thuban will only show improvements due to Turbo, if you run a benchmark on Thuban that doesn't use more than 4 threads, then clock for clock, it will be no faster than the PhII.
What is your prediction?
I see you are falling back to personal insults and pretending that somebody doesn't understand your less than intelligent ranting. You are not revealing unusual behavior for somebody that is desperate.
:lol: You are a funny and confused man Keith. Suggesting I am falling back to insults, when that is your stock in trade.
And what am I supposedly desperate about? This seems to be your deepest desire, that people who think you are a fool, are desperate about something.
VERY HUMOROUS: When people pointed out that the average home user would not really gain much benefit from Turbo, they were denigrated. Now you are going to support that viewpoint which the Intel fans previously ridiculed people for. No, because y Obvous case of double standards.
But sadly for you (and your argument) the benchmarking platforms we are talking about are not normal systems operating in average conditions. Most of the benchmarking reviews were done under optimal conditions that generally guarantee that the i5-750 was hitting max as much as possible. Sorry to point that out and completely ruin your argument.
Well Keith we don't know if the benchmarking conditions are optimal and thus the Windows Scheduler doesn't inhibit Turbo in benchmarking runs.
But the point you are skipping over is that if AMD's turbo works as well or better than Intel's turbo in the benchmarks, then in no way will I seek to diminish that, and would still continue to see the wide range of benchmarks as being representative of the performance difference between each CPU maker.
You mentioned that the 3.2Ghz PhenomII with 6 cores and Turbo won't be as good as the 3.4Ghz Quad core without the turbo-gimmick. (DUH.)
You shouldn't keep sticking to the conversations you imagine you have in your head, but rather read what has been written.
I was comparing the 2.8Ghz Thuban with a top Turbo of 3.2Ghz to the PhII 3.4Ghz. I made that comparison because they look like they will be priced the same.
And yet in the past so many people pretended that the obscure multi-threaded benchmarks showed how much superior their i7 chips because of hyperthreading. Now you want to discount those same benchmarks. It seems you want to have it both ways. Another example of double standards. Then you want to pretend that adding additional cores is not in any way similar to hyperthreading.
Keith you are just desperate and confused. I am not doing what you are suggesting I am doing.
The top of the line Thuban will be AMD's most compelling desktop part on performance alone, but it will be 50% dearer than a PhII 3.4Ghz, so whilst it will beat the PhII in most, if not all benchmarks, it's margin of victory in a good many of those benchmarks will not be so great as to make the 50% price premium seem worth it. Just as I would never buy a i7 more expensive than the 860 or 930, the small performance advantage isn't worth the extra cost.
The Thuban that is priced the same as the PhII 3.4Ghz, will probably lose more benchmarks than it wins against its sibling.
It is for those above reasons that I have stated that I don't see Thuban shaking things up that much, but I doubt you will understand what I have written and instead will imagine something different, so that you can respond once more with utter nonsense.