Originally Posted by Mostafa Wael
Right here we go.
EAS is a completely different breed compared to the conventional HMP system, where it serves an entirely different purpose of achieving the optimal balance between performance and efficiency, with the latter taking the top spot. EAS achieves that via cleverer tasks placement by which the system determines which is the more efficient cluster for the task to be processed, as well as categorising the different tasks into cgroups (top-app, foreground and background, in order from highest priority to lowest priority) by which each cgroup receives its sliver of the available firepower (cpuset). EAS also offers the capability of inflating the perceived load, that's determined by the load trackers, of the task in any of the cgroups via its schedtune.boost setting, and whether the task should be processed by all the cpu cores available or only by the cluster the task has been placed on via its schedtune.prefer_idle setting. One of the key features of EAS is lifting almost all the processing from the governor to the CPU scheduler (no it is not the I/O scheduler, something different) and letting it take much much more control, leaving the CPU governor to only do the frequency determination part, which unsurprisingly relies heavily on data supplied by the scheduler. With all that said, it is easily deduced that EAS is not all about governors and governor settings and the like, rather a much cleverer solution that serves the purpose of seeking the best balance between performance and efficiency, and to ensure the CPU is not overdoing a task or the CPU governor is overshooting, draining a lot of power as a consequence of that. EAS is about ensuring you get the smoothest UI possible while retaining as much power as possible. However, that does not mean that EAS is lame poor when it comes to performance. Sometimes, if not in most cases, this cleverer tasks placement makes tasks get processed faster. Conserving battery does not necessarily mean crushing performance. This explains that app launches are on-par with HMP if not ahead of it sometimes.
Now on to your question. After going through that brief explanation of EAS, i think your question is actually invalid, since it is not an apple-to-apple comparison anymore. EAS seeks for the optimal balance between performance and efficiency. Should there be a commit to improve performance while not being at the expense of efficiency, EAS should have that stuffed in, whereas HMP is prioritising performance higher than efficiency by design. What Burnout does is taking HMP and making it even more performance oriented, hence it is very unlikely to face micro lags with it. However, HMP still misses the cleverer tasks placement, which can show its canines if you have so much processes going in the background, where in that area EAS takes the lead quite noticeably.
Conclusion: You should try and see what suits you more. But something i can safely say is, EAS is more than satisfactory when it comes to performance from the perspective of a man after the best performance, and with the battery gains you yield with EAS, it can go better.
Hope i helped and clear the confusion. Looking forward to your feedback on your EAS experience.
Thanks a lot for this explanation chief !!
I loved you burnut profiles, but I believe I love too much that newx EAS features !
Not sure about battery life yet, since I use it since yesterday, but the ROM feels smoother( except in games, where I have micro stutters, joshuous says it could be caused by sdcardfs module commit, but I didn't catch how desactivating it.. )
But the entire ROM has a feel of more smooth, faster ! Even with a perf oriented profile like burnout_pr4 with Ex kernel
I think render kernel is great, but vertexOS too !!
And if I'm not wrong, it's in early developement, and will maybe better in the future. Maybe it IS the future of kernels..
How do you feel it ?
Anyway, thanks a lot for your feedback and experience sharing !