I have BOINC running in the background, which uses the remaining (idle) CPU cycles.
With 2.6.24-2, other processes now get max. 50% of the available CPU cycles! ~50% of the cycles still go to boinc, although it's running at niceness 19.
Additionally, non-nice load does not change the cpu frequency (from 1.0 to 1.8ghz in my case), when the dynamic cpufreq governor is being used.
I've tested normal cpu load with "cat /dev/urandom > /dev/null", which is expected to max out, but does not so with 2.6.24-2.
I have BOINC running in the background, which uses the remaining (idle) CPU cycles.
With 2.6.24-2, other processes now get max. 50% of the available CPU cycles! ~50% of the cycles still go to boinc, although it's running at niceness 19.
Additionally, non-nice load does not change the cpu frequency (from 1.0 to 1.8ghz in my case), when the dynamic cpufreq governor is being used.
I've tested normal cpu load with "cat /dev/urandom > /dev/null", which is expected to max out, but does not so with 2.6.24-2.