Quote:
Originally Posted by Maxx134
With OCT, I disabled polling with a zero setting, and disabled Dynamic Scaling with a zero setting.
A 2000ms setting for OCT would actually be a good thing, as the app would not be looking to change speed so often.
For OCT app, I personally like a steady overclock for overall better response/snappyness and less chance for SOD..
BUT, With dynamic clock enabled , I can also clock one step higher, but it does not feel any faster, but it may save battery, so it is a mixed bag of compromises.
|
Totally agree!! The jumpy-ness of it just drive me nuts! I've been in IT way too long... A real old article I read once about IT stress levels.. talked about millisecond response time anticipation.. certainly MUCH more then that!!
So if you disable dynamic you're back to what I use... setcpuspeed1d, steady & true... 729 & now works without the 20 in setup... 200 default works great with no SODs on the Sept 20 Qmenu NRG cookie 23xxx build! I started using it when it first came out... updated... still on it. (same as your quoted post at the top of this page) :>))