Umm...exactly, yet again, and you continue to support my original question of your statement. I hope that makes it more clear.
How can they add more units when their architecture doesn't support more units? Magic? :hmm:
That's the reason why Tahiti and Pitcairn have the same configuration. AMD can add more SIMD-Cluster with TMUs and Compute-Units. But at some point the performance benefit is not scaling up with the units.
So, yes, higher clocks - can overcome the difference in through put, which it does.
Yes because of the higher clock you don't need more geometry pipelines and units. But it will increase the power consumption.
It is a problem, just like the lack of tessellation units were for the HD 5k series - which is why I offered that as a comparative from the start.
It's the reversal of the tessellation issue. AMD beat their chest for years, then nVidia stomped them with their implementation. Well nVIdia beat their chest for years, and now AMD is stomping them with their implementation.
It has nothing to do. Kepler is limited by the compute units (Back-End). Using DirectCompute for accelerate the processing time of effects will always benefit Kepler more than Tahiti because Tahiti is limited by the front-end.
That's the reason why AMD is pushing more workload instead of less and Tessellation: It will hurt them more than nVidia.