Related
What's the difference between / features of:
Interactive
Conservative
Ondemand
Smartass
Smartassv2
Performance (is it run at the maximum?)
Powersave (is it run at the minimum?)
And does performance for each vary per kernel? What I mean is will, say, Interactive be better than Conservative on Incredikernel AOSP but worse on Tiny GB Sense?
pianoplayer said:
What's the difference between / features of:
Interactive
Conservative
Ondemand
Smartass
Smartassv2
Performance (is it run at the maximum?)
Powersave (is it run at the minimum?)
And does performance for each vary per kernel? What I mean is will, say, Interactive be better than Conservative on Incredikernel AOSP but worse on Tiny GB Sense?
Click to expand...
Click to collapse
ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
SMARTASS GOVERNOR
Based on the concept of the interactive governor. I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies. Smartass will also cap the max frequency when sleeping to 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245. No need for sleep profiles any more!
The performance for each can varry by kernel due to the fact that some devs slightly tweak the governors to their liking. Without any tweaking they should be the same accross all kernels.
Also note that tinys kernel has an interactive X governor and also a smartass 2 governor. These are basicky just tweaked versions of the original governor.
pianoplayer said:
What's the difference between / features of:
Interactive
Conservative
Ondemand
Smartass
Smartassv2
Performance (is it run at the maximum?)
Powersave (is it run at the minimum?)
And does performance for each vary per kernel? What I mean is will, say, Interactive be better than Conservative on Incredikernel AOSP but worse on Tiny GB Sense?
Click to expand...
Click to collapse
This is a good resource for governors. It is quite technical though. It doesn't include smartass though smartass is similar to smartassv2.
CPU Governors
Let me know if you still have questions after reading it.
The answer to your second question is no. The build of the governors are about 95% the same between kernels and with the exception of the smartass governors all those listed are stock android kernels.
Interactive should be smoother than conservative or ondemand but similar in performance to the smartass governors.
SmartassV2 is found to give the best performance/battery life combo across the board.
Edit: Good writeup cmlusco. In practice yes, smartassv2 is better all around I think. Interactive from Nexus S/Galaxy Nexus kernel source should be good but I've yet to be able to backport it to work on this phone property. It turns into a performance governor really.
And a side note. If the phone is actually in deep sleep state (reported by CPU Spy) the governor will not really matter then. Only time screen off matters is when it's awake but screen is off. Governor is most critical when screen is on really, so if you go for performance, screen on performance is what matters.
Edit 2: And I read some interesting viewpoints recently on maximizing battery that are different than the minimize CPU speed.
Right now I'm at 1.35GHz with Francos stock settings, so 700 for the minimum. Should I expect to see much of a loss in battery life? And what is the difference between the different governors? I could never find much info about them.
The OC itself dosent affect battery, it's how much time your phone is in whatever state(350, 700, 1350, etc..) also setting the minimum to 700 is either really good or really bad for battery, if you turn on your screen ever 5 minutes then it will be better to have it at 700 but if you only turn on your screen once every couple hours you will get much better battery with the absolute minimum. As for governors
Code:
interactive - Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
smartass - Is an improved version of interactive governor
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
brazilianwax - Very agresive version of smartass
interactiveX - Tweaked Interactive governor by Imoseyon by adding more features like suspend/wake profile
ondemandX - Tweaked and ported from 2.6.38 base Ondemand governor by Imoseyon by adding more features like suspend/wake profile
This is taken from the lord module kernel from the desire HD forum as it has a list of many governors, you may have to try a couple governors until you find one that balances speed and battery life for your personal needs, on more governor on our devices is hotplug which will turn off one of the CPU cores when the screen is off.
Seen a lot of conflicting comments stating using smartass governor means there is no need for profiles to be setup and can actually be detriment to the battery life and speed of phone.
Is this true or could I benefit from setting up profiles to get my usage optimised.
Below is a quote which will explain you everything about smartass governor
From it's developer:
"smartass governor - is based on the concept of the interactive governor. I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies. Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 - why?! - it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
Click to expand...
Click to collapse
hey guys, i was just wondering. i have been using badass governor but i
am trying to figure the best io/ scheduler to use with the governor to get best battery..
thanks in advance..
badass is good.
Try with row.
What are your goals here?
I have had the best battery results with Badass2 governor with Row Scheduler and underclocked CPU min 192 max 1188.
What are the best options one gaming performance and second for battery performance. I am currently on zen/ondemand.
note 2
IO does not contribute much to every day performance. Most of the governers should scale to max during games so don't worry about that but if you really want max performance just set it to performance. Best battery life is obviously the power saver governer but honestly for every day performance OnDemand or Pegasusq is the best of both worlds
Currently under clocked at 1.2ghz, in combination with aggressive govr and row sched
What about interactive?