franco notes

I'm currently testing this to ship with r295 (I'm skipping r294 number):

go_hispeed_load: 70, min_sample_time: 50000, timer_rate: 30000

I set my min to 192Mhz (since its slower than my usual 384Mhz I can take account if system is slower or faster with different interactive settings) and I've yet to see any lag. With higher go_high_speed load it takes a little extra time on lower frequencies. timer_rate (default 20k) = cpu frequency transition latency which is 30ms. min_sample_time (default 60k) = minimum rate spend on higher frequencies before it can ramp down.

Would be very nice to cook up some balanced levels to ship the kernel with so keep your tests coming.

-go_hispeed_load:.......higher = better battery, lower = better performance. 50-60 is the sweet spot. (50 is default)
-min_sample_time:......lower = better battery, higher = better performance. 40k-60k is the sweet spot. (60k is default)
-timer_rate:.................higher = better battery, lower = better performance. 20k-30k is the sweet spot. (20k is default)
-above_hispeed_delay: higher = better battery, lower = better performance. 20k-50k is the sweet spot. (100k is default)

The defaults you wrote are wrong, this are the defaults from JellyBean.

cpufreq interactive governor: timer 20ms, min sample 60ms, go_hispeed_load 50%, above_hispeed_delay 100ms


Wow! Lots of great info here! I attempted to split the difference and so far I'm liking the following:

above_hispeed_delay 60000; go_hispeed_load 60; hispeed_freq 1036; min_sample_time 50000; timer_rate 20000.

That looks like it's gonna be a good middle ground.   I think for performance, I'd push to 50k, 50, 40k, 20k (in your order listed). But 60k, 60, 50k, 20k will be a tad bit better for battery.

I tried "50k, 50, 40k, 20k" but things still didn't seem quite as responsive as "60k, 60, 50k, 20k". Not sure why.

r294 over r292, that much I know, especially with the new balanced tunables we're working on.

As far as I know, yellowdie is correct. above_hispeed_delay is how long it waits once the load is above hispeed_load before jumping to hispeed_freq, the idea being maybe the lower freq can handle the load without needing the jump, so it's given time to try.
"Wait this long before raising speed above hispeed, by default a single timer interval." I'd say anything between 30ms and 60ms would be a balanced choice. Default 100ms might be a little to much.

N5 stuff, settings for best battery life:

CPU Manager > Governor Control:

above_hispeed_delay: 150,000
boostpulse_duration:700,000
go_hispeed_load:90
hispeed_freq:1497600
min_sample_time:10000

CPU Manager > Hotplug control:

first_level: 90

CPU Manager > Voltage Control:

300mhz to 700mV
All others -50mV

CPU Manager:
Max CPU Frequency: 1497 or 1574