I found this writeup on overclocking the non-K 10900:
Intel Core i9-10900 Review - Fail at Stock, Impressive when Unlocked - TechPowerup
In our Core i9-10900 review we're taking a close look at what can be gained from unlocking the power limit of this 65 W processor. Results are impressive: up to 40% faster apps and performance that rivals the Core i9-10900K at much lower pricing, but heat output is increased, too.
www.techpowerup.com
Re WhenMusicAttacks's run downs on OC: I'm reading, but also I'm mystified at this way of talking:
I would value the 10850k slightly more because of what i wrote. I had a client that had performance issues while the cpu was just using 80w - enabling all core turbo to 5ghz moved the power on that same worload reach 100w, and solved the stuttering. Even though with Cinebench the scores were almost the same, with the stock config using 150w (undervolted) and doing 2400 and the MCE setting
This paragraph sounds like it says something technical, but what?
• Saying "My client's app stuttered at 80W" is a very peculiar statement. I'm reading between the lines to get the point, but this language leads to absurd thinking. At a technical level, describing app performance in terms of power disparities is a wild figure of speech. While we can observe that clocking up a CPU can improve code speed, and that clocking up has power implications, we can't jump from end-user thermal assessment in watts back to general app suitability to purpose. This way of thinking is like trying to assess African butterfly wing flaps effects on insect migration by taking measurements of the whorl of a Gulf hurricane.
• Benchmarks are never intended to be predictors of performance, they're intended to be a reference by which system changes can be compared. There's an huge gap between making a benchmark comparison and understanding a system balance, so saying that Cinebench stayed the same in the face of thermals is a meaningless point regarding app responsiveness.
For example, if the CPU is bumping up against its rev limiter this can cause oscillation due to hysteresis in feedback of the governor loop. This will manifest as media playback stuttering.
The problem and solution are not in sheer power, but getting the governor configuration to a place the system doesn't oscillate. Note that internally the causes and effects may be extremely complex, but get resolved with a simple config adjustment.
I suggest to everyone that if you can avoid thinking about voltage levels and boost clock over-current time windows, you want to avoid such parameters. How much time do you want to spend twiddling voltage to get a config that doesn't crash, and how transportable is your learning? If there's a custom config for every build, that's a big hazard. OTOH if there's a solid recipe you want it in form of lore, you want it in the board logic so you don't have to futz with it!
For production systems, what you want is for Intel and board maker to produce a stable arrangement at a level of performance against a reference you can test to match your workload. This lets you assess that a system is suitable for a use-case (client), and let's you confirm that config changes don't spoil the setup.
I'm not putting down hard-won experience of gaming PC mindset, but I am pointing out pitfalls of this mindset to understanding system perf. Gamers don't think systematically, they think tactically. They like an incremental advantage for conquest and tend to tolerate big losses in stability to win the fight — like losing all their data. Note that Boxers and football (rugby) players are never the picture of long-term heal. This analysis is my way of coping with the cognitive dissonance of this whole scene, which is largely about making Mac as confusing and unreliable as Windows PC!
To bring this back around, my experience with Asus ROG AI OC is that its trying to simplifies finding a top performing stable configuration without lots of crash testing. It allows hand tailoring of OC voltages and power windows for those who are crazy enough to think like this, but it also makes the tweaking seem passe by wrapping the config up with some simple settings.
There are still many ways to go wrong, because the settings are poorly documented and the OC features are very dynamic. Moreover, if your work depends a build which clocked to the edge of its thermal limit and you suffer through a literal heat wave on big job... But the Asus BIOS does greatly ease finding a sweet spot.
That's my story, an I ain't changin'