News for hackers. Stuff that matters.
Re:Forcing the CPU affinity can make a monothreaded process ... by Erwin on Sunday December 09, 2012 @07:24AM (#4894560)
Using "ondemand" rather than "performance" can do quite a bit for your interactive performance as well. With "ondemand" your CPU runs at half speed until you've stressed it for a bit. So if say, switching to another desktop takes 0.1 cpu seconds, but the threshold is that the CPU must spend 0.5 seconds working before it kicks into full performance then all those UI actions might only execute at half speed.

So personally, I have my desktop CPU (i7) running at performance setting. That was clearly noticeable for me for short bursts of activity. It's possible you could settle on doing that for just some of the cores (I don't know if that makes sense, since they're in a single package).

Re:Forcing the CPU affinity can make a monothreaded process ... by Evbn on Sunday December 09, 2012 @10:54AM (#4894971)
It is extremely unlikely that interactive performance has any human-detectable relation to CPU switching from 1.5Ghz to 3ghz or whatever.

The I/O and Ram paging situation far dominates.

Re:Forcing the CPU affinity can make a monothreaded process ... by darkstalker on Sunday December 09, 2012 @12:05PM (#4895127)
In my case the interactive performance when using "ondemand" is highly noticeable when gaming or while using some apps like Firefox. It seems to be a known problem [1] with GPU intensive tasks.

[1] http://jasondclinton.livejournal.com/72910.html

Re:Forcing the CPU affinity can make a monothreaded process ... by Strshps1MoreTim on Sunday December 09, 2012 @11:42AM (#4895067)
The problem is switching not occurring, or occurring too late - with the OS shuffling a single threaded app around I/O units it looks like the CPU usage is say 20% so no need to move to higher clock.