Wait, let me get this right...so I understand the arguments better...
We count the OC only after the initial OC from GPU Boost? Can i ask why? If the card is set stock at 1006mhz, to me that is stock.
That's how we have always counted any product with dynamic OC --> see CPUs.
Please take 10 min to read the PureOverclock 1 page,
it explains it much better than I do.
GTX680 has less overclocking room because dynamic OC already overclocks part of the way there. That has nothing to do with GTX680 having poor overclocking scaling. What it rather means is 680's have lower overclocking room to gain performance from dynamic base clocks.
GTX680 has 1006 factory clocks.
Its operational clocks are 1110mhz.
Manual overclock is 1300mhz.
How much is that overclock in the real world?
1300mhz / 1110mhz = 17%
Therefore, you should see
at most a 17% performance increase from stock benchmarks, which is exactly what's being shown.
It's the same as we've always counted it with CPUs. This applies to any product with dynamic OC functionality built in. For example, while Core i7 860's stockspeed is 2.8ghz, it turbos at a minimum to 2.93ghz on all 4 cores. If I were to run all my 4 threaded benchmarks with i7 860 and get my Base scores and assign them 100% reference, then compared to those scores a manually overclocked 860 @ 3.2ghz is not 18% faster! It would correct to say that my CPU was overclocked by 14% from "stock clock of 2.8ghz" but it would be INCORRECT to compare benchmarks and look for a 14% growth since the stock 860 never operates at 2.8ghz. It operates at a minimum of 2.93ghz. The largest increase I would see is 9%. Alternatively, imagine if you ran a single threaded bench such as SuperPi. A stock i7 860 would beat a manually overclocked 3.2ghz i7 860. Using your logic, you'd get negative CPU scaling. That's because it's incorrect to use 2.8ghz as the base clock for a Turbo enabled CPU.
For mobile CPUs, the CPU boost is even more. You can have a mobile CPU boost 1ghz from 2ghz. Are you going to say that if you overclocked your CPU to 3.2ghz, that's a 1.2ghz overclock from stock? NO. That's only a 200mhz overclock from factory operational clocks.
So if you are going to look at frequency scaling, the base clock = highest frequency scaling out of the box vs. overclocked highest frequency.
We wouldn't say that a 4.0ghz 2600K is 18% faster clocked than a reference 2600K
with Turbo. We would say a 4.0ghz 2600k has 18% higher frequency than 2600K operating at 3.4ghz. This is because 2600K can turboboost to 3.8ghz. So obviously you'll never see 18% scaling on 2600K @ 4.0ghz over a 2600K with Boost up to 3.8ghz.
The benchmarks are showing this exactly. The base = 100% is likely at minimum 1110mhz, not 1006. So it's 100% incorrect to compare reference benchmarks and then say it's a 30% overclock from 1006 to reference #s because the GPU never operated at 1006mhz. You would say GTX680 has less overclocking headroom since Dynamic OCing has eaten into that headroom with a 7-10% factory dynamic OC.
There is no apparent GPU scaling problem with Kepler, it's simply incorrect use of mathematics using an incorrect 1006mhz as the base for the benchmarks. What Kepler has is a lower overclocking headroom in % terms vs. 7970.