On a related general architectural note, you can assume for all future devices and chipsets we target that we will have at least 2 cores, even in the lowest cost variants. Even 4 cores will become pretty ubiquitous in the low end fairly soon.
Thanks, Andreas On Sep 24, 2014, at 12:33 PM, Mason Chang <[email protected]> wrote: > Hi All, > > We'll be updating the compositor thread priority from a nice value of 0 to a > nice value of -4 in bug 1071156 on b2g. This value matches Android's > compositor thread priority. Having a higher compositor thread priority > enables animations to be a bit smoother and user interactions on screen feel > a bit more responsive. > > We already tested raising the value on a flame on heavy workloads, including > while playing music in the background. (Music has a nice value of -16). > Everything seemed ok. We also did start up tests and noticed a roughly 10-15 > ms regression on some apps which is in the noise range, but we may see a > little start up regression as the compositor takes some CPU time. We think > this is acceptable as animations to open the app are smoother and we can > display content sooner as well. > > I just wanted to give everyone a heads up of something that may affect your > app. Please ping me if you notice other issues. If you want to revert the > compositor back to a nice value of 0, you can change it here - > http://dxr.mozilla.org/mozilla-central/source/b2g/app/b2g.js?from=b2g.js&case=true#754. > > Thanks, > Mason > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
