Why is the overall performance of BD, Vishera and all AMD's processors so low because of the IPC performance. The whole modules vs. core things shouldn't matter, because a lot of benchmarks in use tend to favor integer operations than floating point ones...Anandtech made this a point to test integer and floating point performance.
What's the flaw here? How can AMD be even more inefficient with their processors? The IPC performance of Bulldozer can be seen as worse at times compared to Phenom II.
Does AMD need better engineers? How can they still excel at GPUs, but suck at CPUs? Honest question. No bashing, baiting or flame throwing. I simply don't understand why once leading, now they are lagging especially when they have such talent on the GPU side.
Assuming you are not trolling, which might be a big stretch, here is my answer:
No, it doesn't suck. They just mis-timed the architecture. If you had a clue about product development cycles, you already knew that it takes years from concept to production.Bulldozer was probably frozen as concept well before Conroe surfaced. If you
understand the rationale behind, it is a beautiful concept: Increase integer horsepower, decrease floating point horsepower as those loads can be offloaded to the GPU, specially after the ATI acqusition (fusion concept) Furthermore, more cores can make finish the workload faster. But it needs the software to be aware of the capabilities.
Unfortunately, while the engineering department delivered, the developer relationships team didn't. By the time BD arrived, fusion wasn't cohesive enough as Open CL was just gaining traction, and many high profile applications were still poorly threaded. The software to make BD shine wasn't there. Couple that with a very strong CPU from the competition, and the weak spots of the new concept were exacerbated. But the software is getting there. More and more applications are getting better threaded, or better yet, using Open CL.
Your mentality, like that of many of the blind fans from the blue team, is wrong: "It sucks, IPC per core is lower" Yes, it is, but how about "IPC per whole CPU"? Is it? Not so clear. If you want to be a luddite and live in the past, your choice, keep using your poorly threaded apps because your CPU has very high IPC per core. Some of us will use
whatever that uses the hardware at it full potential. Let me give you a very simple example:
If you have read the reviews, the blue CPUs are faster in photo edition using the software from the big "A" corporation. You would hence think they are better for photo edition. Assume you just got a dSLR and will be working with RAW files, and based on those reviews you think the blue CPUs are faster. But if you analyze the numbers you realize the "A" software is poorly optimized. Their RAW apps, ACR and lightroom are similar. Why use them if you have better alternatives? How about Corel Aftershot pro? OpenCL support and proper multicore support sound much better. Does it deliver? Oh yes, it does. Which CPU is faster there? A simple google search will tell who wins there, and better yet, an FX in Aftershot pro will do it much faster than an i5 in the "A" apps. Even if you are a blue cpu user, aftershot pro will be faster than the "A" apps simply because it harnesses the potential of the CPU better.
"but, but, all the reviewers use the "A" app for benchmark!" Just because they do doesn't mean you have to do it also.
Most of the review websites are followers, not leaders. If one uses an app, the rest follow suit even if the perspective is incomplete. Go back in time, 2001 timeframe to be precise. An influential website used a program called tmpgenc to measure video encoding (AVI to MPEG2) and then, everyone else started using it also. This program happened to be very well optimized for SSE2. The P4 creamed the K7. Everyone claimed the P4 was better for video encoding. However, the real users of MPEG2 knew quite well that the quality of tmpgenc was mediocre, and that even with its SSE2 optimizations, it was much slower than CCE (Cinema craft Encoder) which happened to run faster on a K7. REAL user kept using CCE, while all the wannabes went with tmpgenc and kept spreading the false premise that the P4 was faster for MPEG2 encoding.
Fast forward to today, and the situation has stayed the same. If one influential site uses a program, the sheep follow. If you have a multicore CPU, regardless of brand, why handicap it?
Get the software that leverages its power the best. I am not going to reward the incompetence of some software companies that fail to use my hardware at its fullest, even if they are the "standard". I have stated before that
benchmark numbers are like car loan applications, you better read the fine print and make sense of the numbers, understanding why they are what they are. f you are OK bragging about your "monster IPC", fine, I will just borrow a quote from a fellow ATer (who happens to use Intel btw) "Those of us who care about productivity, use the right tool..." And it happens that the right tool can mean different software
ps. Hopefully some reviewers get the hint, and start diversifying the test suite. The Corel portfolio really deserves to be included, as they have been pushing proper multithreading and Open CL support. As a user, even if you have an i5 and the FX happens to run faster in those, your i5 will still be faster than using the other program. Ignore the bragging right, enjoy the added productivity.
pss. Wonder if we would be having these discussion had the developer relationships team at AMD had done a better job helping optimize software.