2009-08-11, 09:06
I noticed something strange regarding the multireaded decoding on Jaunty. Even if i apply the command for making more balanced core load, i still have poor performance if i have Intel speedstep enabled in bios.
Yes, removing powernowd does not help. I realized that even if i remove powernowd i have the CPU clocked down to 1600Mhz at 80% CPU load ! Sometimes it ocassionaly clocks up the CPU to 2500Mhz, but than it goes down to 1600Mhz with a lot of framedrops.
Only if i turn off EIST and C1 states in BIOS than i have multireaded performance like it was in Hardy.
I think that there is some kind of CPU scaling in the kernel no mater if you use powernowd or not. There was someething new in kernels later than Hardy's that controls cpu clocks. What i don't understand is why it holds back cpu clock so agressively, when we have a lot of framedrops.
Any idea ?
Yes, removing powernowd does not help. I realized that even if i remove powernowd i have the CPU clocked down to 1600Mhz at 80% CPU load ! Sometimes it ocassionaly clocks up the CPU to 2500Mhz, but than it goes down to 1600Mhz with a lot of framedrops.
Only if i turn off EIST and C1 states in BIOS than i have multireaded performance like it was in Hardy.
I think that there is some kind of CPU scaling in the kernel no mater if you use powernowd or not. There was someething new in kernels later than Hardy's that controls cpu clocks. What i don't understand is why it holds back cpu clock so agressively, when we have a lot of framedrops.
Any idea ?