Confirm, emeritus
2,974
edits
Changes
m
[https://bugzilla.mozilla.org/show_bug.cgi?id=1361474 Interpreter ICs]: This will improve interpreter speed increasing the performance of JavaScript on sites and apps. (2019)
→Fast
[https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/ WebRender]: With WebRender, we want web apps to run at a silky smooth 60 frames per second (FPS) no matter how big the display is or how much of the page is changing from frame to frame. Initial releases will be for selected Nvidia GPUs. (Firefox 6467, limited roll-out.)
[https://mozillagfx.wordpress.com/2018/01/09/retained-display-lists/ Retained Display List]: Gecko will retain the display list between paints, only building a new display list for the parts of the page that changed since we last painted and then merge the new list into the old to get an updated list. (Firefox 61)
[https://mozillagfx.wordpress.com/2017/12/05/off-main-thread-painting/ Off Main Thread Painting]: With OMTP the visual state of the page is still computed on the main thread, but the potentially costly task of rasterization is passed off to a designated “rasterization thread”, and the main thread can carry on and stay responsive. (Firefox 58 on Windows, 59 on Mac)
[https://bugzilla.mozilla.org/show_bug.cgi?id=1385403 OOP Extensions for Mac] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1357487 Linux]: We've already shipped out of process extensions for Windows leading to faster page loads and more browser responsiveness. This year we'll catch up on Mac and Linux. (Mac 61, Linux 201863)
[https://bugzilla.mozilla.org/show_bug.cgi?id=1406181 Replace storage.local] implementation: For improved extension performance, we will replace the storage.local implementation with something more efficient. (62)
[https://bugzilla.mozilla.org/show_bug.cgi?id=1336227 Faster startup first paint]: Firefox will show a browser window as soon as possible after startup, not waiting on the full stack to load. (63)
[https://bugzilla.mozilla.org/show_bug.cgi?id=1401624 Object-biased NaN Boxing]: a lot of code containing small loops do not benefit from any sort of optimization strategy. With Object-biased NaN boxing, we will see improved web page JavaScript performance. (201865)
=== Personal ===
