Jump to content



Photo
- - - - -

Android - CPU Governor's Explained


  • Please log in to reply
6 replies to this topic

#1 theking

theking

    RIM Addict

  • RIM Addict
  • PipPipPipPipPip
  • 570 posts
  • Full Name: theking
  • City: Vadodara
  • Network:Airtel
  • Handset: - Select Handset -
  • Handset - II: - Select Handset -
  • Other Handset:HTC One X

Posted 19 August 2012 - 07:36 PM

I had read the CPU governor's explaination somewhere and had saved as a word doc to my laptop...
Thought to share the info...but cannot give credit to the writer since I cannot recall the link/forum..

CPU frequencies can be set with SetCpu which is a paid apk in the market but available free here:
http://forum.xda-dev...ad.php?t=505419


Android CPU governors explained



1: OnDemand
2: OndemandX
3: Performance
4: Powersave
5: Conservative
6: Userspace
7: Min Max
8: Interactive
9: InteractiveX
10: Smartass
11: SmartassV2
12: Scary
13: Lagfree
14: Smoothass
15: Brazilianwax
16: SavagedZen
17: Lazy
18: Lionheart
19: LionheartX
20: Intellidemand
21: Hotplug
22: BadAss
23: Wheatley
24: Lulzactive
25: Pegasusq/Pegasusd
26: hotplugx
27: AbissPlug



1: OnDemand Governor:
This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.

OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to bitch about performance than they are the few hours of extra battery life another governor could have granted them.

This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.


2: OndemandX:
Basically an ondemand with suspend/wake profiles. This governor is supposed to be a battery friendly ondemand. When screen is off, max frequency is capped at 500 mhz. Even though ondemand is the default governor in many kernel and is considered safe/stable, the support for ondemand/ondemandX depends on CPU capability to do fast frequency switching which are very low latency frequency transitions. I have read somewhere that the performance of ondemand/ondemandx were significantly varying for different i/o schedulers. This is not true for most of the other governors. I personally feel ondemand/ondemandx goes best with SIO I/O scheduler.


3: Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).


4: Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.


5:Conservative Governor:
This biases the phone to prefer the lowest possible clockspeed as often as possible. In other words, a larger and more persistent load must be placed on the CPU before the conservative governor will be prompted to raise the CPU clockspeed. Depending on how the developer has implemented this governor, and the minimum clockspeed chosen by the user, the conservative governor can introduce choppy performance. On the other hand, it can be good for battery life.

The Conservative Governor is also frequently described as a "slow OnDemand," if that helps to give you a more complete picture of its functionality.


6: Userspace Governor:
This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency. This governor is more common amongst servers or desktop PCs where an application (like a power profile app) needs privileges to set the CPU clockspeed.


7: Min Max
well this governor makes use of only min & maximum frequency based on workload... no intermediate frequencies are used.


8: Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.

Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.

However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.

Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.


9: InteractiveX Governor:
Created by kernel developer "Imoseyon," the InteractiveX governor is based heavily on the Interactive governor, enhanced with tuned timer parameters to better balance battery vs. performance. The InteractiveX governor's defining feature, however, is that it locks the CPU frequency to the user's lowest defined speed when the screen is off.


10: Smartass
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!"


11: SmartassV2:
Version 2 of the original smartass governor from Erasmux. Another favorite for many a people. The governor aim for an "ideal frequency", and ramp up more aggressively towards this freq and less aggressive after. It uses different ideal frequencies for screen on and screen off, namely awake_ideal_freq and sleep_ideal_freq. This governor scales down CPU very fast (to hit sleep_ideal_freq soon) while screen is off and scales up rapidly to awake_ideal_freq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery.


12: Scary
A new governor wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.


13: Lagfree:
Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly. Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little.


14: Smoothass:
The same as the Smartass “governor” But MUCH more aggressive & across the board this one has a better battery life that is about a third better than stock KERNEL


15: Brazilianwax:
Similar to smartassV2. More aggressive ramping, so more performance, less battery


16: SavagedZen:
Another smartassV2 based governor. Achieves good balance between performance & battery as compared to brazilianwax.


17: Lazy:
This governor from Ezekeel is basically an ondemand with an additional parameter min_time_state to specify the minimum time CPU stays on a frequency before scaling up/down. The Idea here is to eliminate any instabilities caused by fast frequency switching by ondemand. Lazy governor polls more often than ondemand, but changes frequency only after completing min_time_state on a step overriding sampling interval. Lazy also has a screenoff_maxfreq parameter which when enabled will cause the governor to always select the maximum frequency while the screen is off.


18: Lionheart:
Lionheart is a conservative-based governor which is based on samsung's update3 source.
The tunables (such as the thresholds and sampling rate) were changed so the governor behaves more like the performance one, at the cost of battery as the scaling is very aggressive.


19: LionheartX
LionheartX is based on Lionheart but has a few changes on the tunables and features a suspend profile based on Smartass governor.


20: Intellidemand:
Intellidemand aka Intelligent Ondemand from Faux is yet another governor that's based on ondemand. Unlike what some users believe, this governor is not the replacement for OC Daemon (Having different governors for sleep and awake). The original intellidemand behaves differently according to GPU usage. When GPU is really busy (gaming, maps, benchmarking, etc) intellidemand behaves like ondemand. When GPU is 'idling' (or moderately busy), intellidemand limits max frequency to a step depending on frequencies available in your device/kernel for saving battery. This is called browsing mode. We can see some 'traces' of interactive governor here. Frequency scale-up decision is made based on idling time of CPU. Lower idling time (<20%) causes CPU to scale-up from current frequency. Frequency scale-down happens at steps=5% of max frequency. (This parameter is tunable only in conservative, among the popular governors)
To sum up, this is an intelligent ondemand that enters browsing mode to limit max frequency when GPU is idling, and (exits browsing mode) behaves like ondemand when GPU is busy; to deliver performance for gaming and such. Intellidemand does not jump to highest frequency when screen is off.


21: Hotplug Governor:
The Hotplug governor performs very similarly to the OnDemand governor, with the added benefit of being more precise about how it steps down through the kernel's frequency table as the governor measures the user's CPU load. However, the Hotplug governor's defining feature is its ability to turn unused CPU cores off during periods of low CPU utilization. This is known as "hotplugging."

22: BadAss Governor:
Badass removes all of this "fast peaking" to the max frequency. On a typical system the cpu won't go above 918Mhz and therefore stay cool and will use less power. To trigger a frequency increase, the system must run a bit @ 918Mhz with high load, then the frequency is bumped to 1188Mhz. If that is still not enough the governor gives you full throttle. (this transition should not take longer than 1-2 seconds, depending on the load your system is experiencing)
Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1188Mhz. If the gpu is crushed under load, badass will lift the restrictions to the cpu.

23: Wheatley:
Building on the classic 'ondemand' governor is implemented Wheatley governor. The governor has two additional parameters:

target_residency - The minimum average residency in µs which is considered acceptable for a proper efficient usage of the C4 state. Default is 10000 = 10ms.

allowed_misses - The number sampling intervals in a row the average residency is allowed to be lower than target_residency before the governor reduces the frequency. This ensures that the governor is not too aggressive in scaling down the frequency and reduces it just because some background process was temporarily causing a larger number of wakeups. The default is 5.
Wheatley works as planned and does not hinder the proper C4 usage for task where the C4 can be used properly .
For internet browsing the time spend in C4 has increased by 10% points and the average residency has increased by about 1ms. I guess these differences are mostly due to the different browsing behaviour (I spend the last time more multi-tabbing). But at least we can say that Wheatley does not interfere with the proper use of the C4 state during 'light' tasks. For music playback with screen off the time spend in C4 is practically unchanged, however the average residency is reduced from around 30ms to around 18ms, but this is still more than acceptable.

So the results show that Wheatley works as intended and ensures that the C4 state is used whenever the task allows a proper efficient usage of the C4 state. For more demanding tasks which cause a large number of wakeups and prevent the efficient usage of the C4 state, the governor resorts to the next best power saving mechanism and scales down the frequency. So with the new highly-flexible Wheatley governor one can have the best of both worlds.

Obviously, this governor is only available on multi-core devices.

24: Lulzactive:
Lulzactive:
This new find from Tegrak is based on Interactive & Smartass governors and is one of the favorites.
Old Version: When workload is greater than or equal to 60%, the governor scales up CPU to next higher step. When workload is less than 60%, governor scales down CPU to next lower step. When screen is off, frequency is locked to global scaling minimum frequency.
New Version: Three more user configurable parameters: inc_cpu_load, pump_up_step, pump_down_step. Unlike older version, this one gives more control for the user. We can set the threshold at which governor decides to scale up/down. We can also set number of frequency steps to be skipped while polling up and down.
When workload greater than or equal to inc_cpu_load, governor scales CPU pump_up_step steps up. When workload is less than inc_cpu_load, governor scales CPU down pump_down_step steps down.
Example:
Consider
inc_cpu_load=70
pump_up_step=2
pump_down_step=1
If current frequency=200, Every up_sampling_time Us if cpu load >= 70%, cpu is scaled up 2 steps - to 800.
If current frequency =1200, Every down_sampling_time Us if cpu load < 70%, cpu is scaled down 1 step - to 1000.

25: Pegasusq/Pegasusd

The Pegasus-q / d is a multi-core based on the Ondemand governor and governor with integrated hot-plugging.
Ongoing processes in the queue, we know that multiple processes can run simultaneously on. These processes are active in an array, which is a field called "Run Queue" queue that is ongoing, with their priority values ​​arranged (priority will be used by the task scheduler, which then decides which process to run next).

To ensure that each process has its fair share of resources, each running for a certain period and will eventually stop and then again placed in the queue until it is your turn again. If a program is terminated, so that others can run the program with the highest priority in the current queue is executed.

26: hotplugx

It 'a Hotplug modified and optimized for the suspension in off-screen

27: AbissPlug

It 'a Governor derived hotplug, it works the same way, but with the changes in savings for a better battery.


I use Smartassv2 or Interactivex....
Don't Follow Your Shadow, Lead It!!

#2 amtrag

amtrag

    RIM Veteran

  • RIM Veteran
  • PipPipPipPipPipPip
  • 813 posts
  • Full Name: Anurag
  • City: Mumbai
  • Network:Reliance CDMA
  • Handset: Not Listed
  • Handset - II: HTC Incredible
  • Other Handset:Samsung Galaxy Nexus LTE

Posted 20 August 2012 - 11:53 AM

Thanks for the useful info.

#3 Honest

Honest

    The Observer.....(Observing Everything)

  • Super Moderators
  • PipPipPipPipPipPip
  • 6,830 posts
  • Full Name: Kamal
  • City: Mumbai
  • Network:Reliance CDMA
  • Handset: LG FWP LSP 340E
  • Handset - II: Samsung Galaxy Chat GT-B5330
  • Other Handset:Samsung Galaxy S Duos

Posted 21 August 2012 - 09:36 PM

Thanks for the useful info King Bhai. +1 :)
तू हर घड़ी, हर वक़्त, मेरे साथ रहा है,
हाँ ये जिस्म कभी दूर, कभी पास रहा है,
जो भी ग़म हैं ये तेरे, उन्हें तू मेरा पता दे,
कुछ इस तरह तेरी पलकें, मेरी पलकों से मिला दे,

आँसू तेरे सारे, मेरी पलकों पे सजा दे.......

Important Links :

• Lets Ask Arun • When You Will Be Available On Rimweb.in Next

• What's Your "Typing Speed" • Do You Love Rimweb ?

• Discuss here about any doubts and querries about HIV / AIDS

• Forum Buy / Sell Guidelines

• Golden Oldies (Old Is Gold) • Tashan Of Rimweb (MP4 Video Caller Tunes)

~ If you need any help on the forum, then don't hesitate to ask or PM me


#4 Abhishek Pujar

Abhishek Pujar

    Member

  • Members Group
  • PipPip
  • 15 posts
  • Full Name: abhishek
  • City: Mangalore
  • Network:Reliance CDMA
  • Handset: Not Listed
  • Handset - II: Not Listed
  • Other Handset:HTC EVO LTE

Posted 10 December 2012 - 10:16 PM

very useful info :) undervolting should also be considered by users who want a better battery.

#5 praveenwarrier

praveenwarrier

    Advanced Member

  • Experienced Member
  • PipPipPip
  • 148 posts
  • Full Name: PRAVEEN WARRIER
  • City: Navi Mumbai (New Mumbai)
  • Network:Reliance CDMA
  • Handset: Samsung Galaxy S2
  • Handset - II: GSM Handset
  • Other Handset:iPad Air

Posted 12 December 2012 - 11:47 AM

I am on FI03 using epic touch. I am not getting many of these governors under setCPU.. What could be wrong??? Only performance, on demand, powersave are seen.. Downloaded the apk from XDA link given.. Pls let me know..

Sent from my SPH-D710 using Tapatalk 2



#6 phonegeek

phonegeek

    RIM Veteran

  • RIM Guru
  • PipPipPipPipPipPip
  • 1,300 posts
  • Full Name: Saurabh
  • City: Mumbai
  • Network:- Not Selected-
  • Handset: Not Listed
  • Handset - II: GSM Handset

Posted 12 December 2012 - 12:53 PM

You need to have kernel which has all these options. Explore more on XDA, you will definitely find it.

If my post is helpful to you or you liked it, please click rep_up.png

 

 

 

 

 


#7 rajanmehta

rajanmehta

    You're Unique, Just Like Everyone Else

  • Super Moderators
  • PipPipPipPipPipPip
  • 4,162 posts
  • Full Name: Rajan Mehta
  • City: Thane
  • Network:Reliance CDMA
  • Handset: HTC EVO 3D
  • Handset - II: - Select Handset -

Posted 14 December 2012 - 11:45 PM

Remaining Good info About CPU Scheduler
 
What is a scheduler? 
In a multitasking operating system, there must be an instance, the processes that want to run, CPU time and allocates it "goes to sleep" after the allotted time (timeslice) again. This instance is called the scheduler, such as opening and closing applications. that is, how fast they are open and how long they are kept in RAM. 
 
I / O scheduler can have many purposes like: 
To minimize time searching on the hard disk 
Set priorities for specific process requests 
To regulate a particular portion of the bandwidth of the data carrier to each running process
To guarantee certain process requests within a certain time 
 
Which scheduler are available? 
CFQ 
Deadline 
VR 
Simple 
Noop 
Anticipatory 
BFQ 
Sio 
 
Anticipatory: 
Two important things here are indicative of that event: 
- Looking on the flash drive is very slow from Equip 
- Write operations while at any time are processed, however, be read operations preferred, ie, this scheduler returns the read operations a higher priority than the write operations. 
 
Benefits: 
- Requests of read accesses are never treated secondarily, that has equally good reading performance on flash drives like the noop 
 
Disadvantages: 
- Requests from process operations are not always available 
- Reduced write performance on high-performance hard drives 
 
CFQ: 
The CFQ - Completely Fair Queuing - similar to the Dead Line maintains a scalable continuous Prozess-I/O-Warteschlange, ie the available I / O bandwidth tried fairly and evenly to all I / O requests to distribute. He created a statistics between blocks and processes. With these statistics it can "guess" when the next block is requested by what process, ie each process queue contains requests of synchronous processes, which in turn is dependent upon the priority of the original process. There is a V2 and the CFQ has some fixes, such as were the I / O request, hunger, and some small search backward integrated to improve the responsiveness. 
 
Benefits: 
- Has the goal of a balanced I / O performance to deliver 
- The easiest way to set 
- Excellent on multiprocessor systems 
- Best performance of the database after the deadline 
 
Disadvantages: 
- Some reported user that the media scanning would take this very very long time and this by the very fair and even distribution of bandwidth on the I / O operations during the boot process is conditioned with the media scanning is not necessarily the highest should have priority 
- Jitter (worst case delay) can sometimes be very high because the number of competing with each other process tasks 
 
Deadline: 
This scheduler has the goal of reducing I / O wait time of a process of inquiry. This is done using the block numbers of the data on the drive. This also blocks an outlying block numbers are processed, each request receives a maximum delivery time. This is in addition to the Governor BFQ very popular and in many well known kernels, such as the Nexus S Netarchy. He was indeed better than the BFQ, but compared to the VR he will be weaker. 
 
Benefits: 
- Is nearly a real-time scheduler. 
- Characterized by reducing the waiting time of each process from - best scheduler for database access and queries. 
- Bandwidth requirements of a process, eg what percentage does a CPU is easy to calculate. 
- As the Governor-noop ideal for flash drives 
 
Disadvantages: 
- If the system is overloaded, can go a lost set of processes, and is not as easy to predict 
 
SIO: 
It aims to achieve with minimal effort at a low latency I / O requests. Not a priority to put in queue, instead simply merge the requests. This scheduler is a mix between the noop and deadline. With him there is no conversion or sorting of requests. 
 
Benefits: 
- It is simple and stable. - Minimized Starvations (starvation) for inquiries 
 
Disadvantages: 
- Slow random write speeds on flash drives as opposed to other schedulers. - Sequential read speeds on flash drives, not as good 
 
Noop: 
The noop scheduler is the simplest of them. He is best suited for storage devices that are not subject to mechanical movements, such as our flash drives in our SGSII's to use to access the data. The advantage is that flash drives do not require rearrangement of the I / O requests, unlike normal hard drives. ie the data that come first are written first. He's basically not a real scheduler, as it leaves the scheduling of the hardware. 
 
Benefits: 
- Adds all incoming I / O requests in a first-come-who-first-served queue and implements requests with the fewest number of CPU cycles, so also battery friendly 
- Is suitable for flash drives because there is no search errors 
- Good data throughput on db systems 
 
Disadvantages: 
- Reducing the number of CPU cycles corresponds to a simultaneous decline in performance 
 
VR: 
Unlike other scheduling software, synchronous and asynchronous requests are not handled separately, but it will impose a fair and balanced within this deadline requests, that the next request to be served is a function of distance from the last request. The VR is a very good scheduler with elements of the deadline scheduler. He will probably be the best for MTD Android devices. He is the one who can make the most of the benchmark points, but he is also an unstable schedulers, because his performance falter. Sometimes they fluctuate below the average, sometimes it fluctuates above the average, but if above, then he is the best. 
 
Benefits: 
- Is the best scheduler for benchmarks 
 
Disadvantages: 
- Performance variability can lead to different results 
- Very often unstable or unzverlässig 
 
Simple: 
As the name suggests, it is more of a simple or simple scheduler. Especially suitable for EMMC devices. He is reliable, maybe not as good as the VR, when this time has a good day, but he is despite all this very performance-based and does his best. At the moment it is the default scheduler in quasar kernel. 
 
Advantages: - not known 
Cons: - not known 
 
BFQ: 
Instead requests divided into time segments as the CFQ has, on the BFQ budget. The flash drive will be granted an active process until it has exhausted its budget (number of sectors on the flash drive). The awards BFQ high budget does not read tasks. 
 
Benefits: 
- Has a very good USB data transfer rate. 
- Be the best scheduler for playback of HD video recording and video streaming (due to less jitter than CFQ Scheduler, and others) 
- Regarded as a very precise working Scheduler 
- Delivers 30% more throughput than CFQ 
 
Disadvantages: 
- Not the best scheduler for benchmarks - higher budgets that were allocated to a process that can affect the interactivity and bring with it increased latency. 
 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users