[Sprint Samsung Galaxy S III] freecharlesmanson:
In this thread we will discuss governors.

Primarily differences between ondemand and conservative based ones. This thread was created because ktoonsez made a hotpluging conservative governor. ... perhaps this needs explanation for the general community, that will imo prove the vast superiority of conservative based governors. First here is a link about governors in general it is sort of abridged but, covers allot of governors http://blog.g4team.com/?p=5519

As you can see it makes mention that most of these governors are similar to ondemand. So outlining the major differences. Ondemand scales to the highest frequency as soon as a load occurs. Conservative scales upward based on the frequency step variable which means for the most part will scale through every frequency to achieve the target load thresholds. What this practically means is ondemand is prone to wasting power on unneeded clock cycles. Ondemand also features something called a down differential, this variable determines how long the governor will remain at the given frequency before scaling down. Conservative does not have this, but instead relies on having a down threshold which insures that as soon as the load drops below a given variable it scales down as fast as the sampling rate allows. The result to this is a governor which attempts to keep the load level tolerable and save you battery! Now ! Ktoonservative Is that but in addition contains a hotpluging variable which determines when the second core comes online. The governor shuts the core off when it drops below the hotplug down threshold thus giving us a handle on the second performance factor in our CPUs behavior. While by default conservative is a poor performer it can be made to perform comparably to even performance governor. Here are some settings to discuss and start with. They are slightly less battery friendly under a load but very very well performing.

after realizing just everything mpdecision does i recommend turning it off for this govenor to work properly "stop mpdecision" in the terminal should do. it not only allows for things like benchmarks to lock frequency but generally will disturb these settings under a load, it will do something completely different. so when i turned it off i discovered the govenor behaving differently....more over exactly as you would expect this also meant with some ideas from mw86 that we dont really need touch booster. id recommend the first set of settings and use the last if you want mpdecision on. despite looking less aggressive for battery savings they usually will be with the absence of mpdecision

SAMPLING_RATE="15000"

UP_THRESHOLD="67"

DOWN_THRESHOLD="47"

FREQ_STEP="3"

SAMPLING_DOWN_FACTOR="1"

IGNORE_NICE_LOAD="0"

UP_THRESHOLD_HOTPLUG="85"

DOWN_THRESHOLD_HOTPLUG="33"

SAMPLING_RATE="40000"

UP_THRESHOLD="67"

DOWN_THRESHOLD="52"

FREQ_STEP="5"

SAMPLING_DOWN_FACTOR="1"

IGNORE_NICE_LOAD="0"

UP_THRESHOLD_HOTPLUG="68"

DOWN_THRESHOLD_HOTPLUG="40"

And here is the link for the kernel containing such http://xdaforums.com/showthread.php?t=1800576

A further edit for jb builds most benchmarks are niced so you must turn off ignore nice load to test settings with them