Quote Originally Posted by eNTi View Post
it's a terrible terrible idea to let the cpu run at it's BOOST speed. that's a surefire kill.
Why "kill"? TurboBoost is Intel's idea.
Quote Originally Posted by eNTi View Post
not to mention the excess heat and noise from my fans.
Yes, that's the only problem.
Quote Originally Posted by eNTi View Post
still there must be a way to optimize the code
Of course there is, every code can be optimized. But someone has to do it, so don't demand the work to be done unless you're willing to pay the salaries.
Quote Originally Posted by eNTi View Post
it's cpu hungry.
No, it's not. It does great even on slow CPUs - as long as they don't grind into full stop when power is most needed.


Modern CPUs employ extremely aggressive power saving mechanisms. That's where power savings come from: the moment CPU thinks it has little to do, it slows down and/or stops. The problem is, it's not as smart as it should be, and CPU often stops when is most needed. And apparently, the way NC is written either misleads power saving mechanisms or makes the results of a slowdown especially noticeable to users (but Massaker's remark about Battlefield suggest it's a problem not limited to NC).
This is why disabling "Enhanced Intel SpeedStep Technology" fixes the problem, at great cost of heat and noise.

There are many SpeedStep settings between "max saving" and "full power" so probably there is something that can prevent problems yet still yield some power savings. So, make comprehensive tests, find the optimal setting and share the knowledge.