* When sys.use_fifo_ui is enabled, ActivityManager tracks the UI thread and RenderThread (the two most UI-critical threads) of the top application and makes those threads SCHED_FIFO instead of SCHED_OTHER. This effectively eliminates jitter from UI and RenderThreads; the traces that've gathered with this option enabled show runnable times on the order of microseconds instead of milliseconds. * However, it should be enabled only when we have EAS i.e a capacity-aware RT scheduler because if RT load balancer is not capacity-aware, then there would be a 30% reduction in application startup performance. Reference: https://source.android.com/devices/tech/debug/jank_jitter Signed-off-by: Saurabh Charde <saurabhchardereal@gmail.com> Signed-off-by: Aston-Martinn <advaithbhat9@gmail.com> Change-Id: I8b55ad1899be985fc7357abaf06d68d6a130fb75 |
||
---|---|---|
.. | ||
init.class_main.sh | ||
init.goodix.sh | ||
init.qcom.post_boot.sh | ||
init.qcom.sh | ||
init.qcom.usb.sh |