[Nexus 4 Original Android Development] Hanny:
Thanks hospital, your hotplugging values are very innovative. I was astonished while it being simple, we didn't think of that before!

On 90-50-30, I have been experiencing micro-stutters during transition animations, and only during transition animations, to name a few, the most memorable one would be after clicking on the whatsapp notification from the notification area.

I think I need more time before commenting on my normal-usage experience on your 90-25-50, but I believe it would eliminate micro-stutters as much as possible. If there are still some existing, its the time for governor control tweaking.

By the way,

r119 & r120 gaming tests

These days were my busy days so no screenshots, post and bye :p

throttling threshold = 85

thalamus hotplugging google interactive 29-31

mpdecison google interactive 31-33

mpdecision conservative 35-37

mpdecision lazy 29-32

mpdecision codeaurora interactive (original) 32-34

mpdecision codeaurora interactive (tweaked) 30-32

m1 interactive (timer_rate=20000) 30-32

r110 interactive (default timer_rate=50000) 28-31

r110 interactive (manual timer_rate=20000) 32-34

#franco-hotplugging era begins#

r115 interactive (default timer_rate=50000) (default_first_level=70) 30-31

r116 interactive (default timer_rate=30000) (default_first_level=80) 32-33 / 34-35

r118 interactive (default timer_rate=30000) (default_first_level=90) 32

r118 interactive 1512/1512 (default timer_rate=30000) (default_first_level=90) 37-38 =proving fps now depends more on freq than hotplug

r119 interactive (default hotplugging90-50-30) (manual timer_rate=20000) (default min_sample_time=45000) 33-34

r119 interactive (default hotplugging90-50-30) (manual timer_rate=20000) (manual min_sample_time=30000) 33-34

r120 interactive (everything default) 31-32

r120 interactive (everything default but input_boost=0) 31-32

r120 interactive (everything default, input_boost=1, hispeed=1026) 31-32

r120 interactive (everything default, input_boost=1, hispeed=1026, gohispeedload=95) 31-32

r120 interactive (everything default, input_boost=1, hispeed=1026, gohispeedload=90) 31-32

r120 interactive (everything default, input_boost=1, hispeed=1350, gohispeedload=95) 31-32

r120 interactive (everything default, input_boost=1, hispeed=1350, gohispeedload=90) 31-32

I hoped, but there were no surprises. its always something around 32 and I would like to make some debrief based on the results I got.

First and foremost, in terms of hotplugging values, as long as the values allows 4 cores to facilitate in gaming, the hotplugging will not affect gaming performance anymore, given that the game is heavy enough to load 90% and doesnt drop below third_level frequently. (I would say most of the 3D games requiring additional data/obb is heavy enough, and for those which doesnt, I would say it differs, for example Beach Buggy is enough for keeping 4 cores but Temple Run 2 fails to maintain >30% load)

as a cheerful fact, hospital's 90-25-50 does not make any drop of cores in gaming, so we can still enjoy one of the major benefits of the new hotplugging driver, while being much more conservative in offflining cores in normal usage. :)

Second, the effect of input_boost depends on the game type and gaming style. In GTA's driving, we do not move our fingers for those certain pixels as we just press and hold. Therefore in the above results there were no change of average fps after altering input_boost. For fruit ninja type of crazy swiping stuff, the cpu would probably constantly boost to franco's boost freqeuncy which is currently 1026, and of course a higher fps.

Third, hispeedfreq and gohispeedload do not pretty much affect the fps in gaming, cause I don't think even the heaviest game out there would stress the CPU at 9X load constantly, while our gohispeedload will probably stay at 9X, there don't seem to be a relevance between them. What's awesome about franco's hotplugging driver is that once the load goes above 90 for once and does not go below third_level, they cores won't go offline!

Finally, no matter in mpdecision or hotplugging, timer_rate does affect fps while min_sample_time does not. However, as franco have stated clearly, a low timer_rate can easily drain your battery fast, so be ready if you'd like to tweak this. And the simple conclusion from these debrief messages can be drawn: If we are going to modify those gov control values for whatever sake, we can be assured that they don't affect gaming experience. As well as hotplugging - 50 as third_level is still good enough for heavy games to maintain 4 cores.