Yea that's fine, I'm not saying hitting max frequency results in throttling.This is in no way contradicting what I claimed. I just said as per cerny max clock speed doesn't imply max power draw. Very well optimized games would find the powerdraw limits and we really don't know what that means. Cerny was very specific on mentioning avx2 for cpu side. And cerny was very specific saying gpu clock speed is not limited by thermals/power draw but some internal implementation of gpu. It just doesn't clock any higher no matter what.
Taking what cerny said it means that to hit those power draw limits one would have to have sufficiently well optimized code. Again what that really means we will not know until some developer spills the beans. Though just hitting max clocks is not enough to cause throttling.
Cerny provided:
a) The optimal clock rates for both CPU and GPU (we anticipate this to be not heavy saturation workloads)
b) Cerny provided the use cases in which CPU load could have a downclocking effect on GPU load. In this case, he brought up AVX calls as being able to drop GPU frequency, but barely. This makes sense because GPU requires 4x more power than CPU in modern GPUs. So if the CPU needs some, the GPU loses it at 1/4 the amount that CPU needs.
c) Cerny _did not_ provide the GPU loads that will cause downclocking on the CPU. The GPU needs to pull 4x the amount in the opposite direction.
d) Cerny _did not_ provide what happens when both CPU and GPU are sufficiently loaded what the frequencies would be