The first of those longer term multi-process features is to go from one content process to multiple content processes. In parallel to work enabling multi-process for more people using Firefox, we’re also working on additional longer term multi-process features that will further improve responsiveness and bring significant security benefits. In Firefox 51, if all testing goes according to plan, we’ll be enabling multi-process Firefox for users with extensions that are not explicitly marked as incompatible with multi-process Firefox. Our measurements and user feedback were all positive and so with Firefox 50 we deployed multi-process Firefox to users with a broader set of extensions, those whose authors have marked them as multi-process compatible.īeyond Firefox 50, we have more work to do to enable multi-process Firefox for users with as yet unsupported extensions.
With Firefox 49 we deployed multi-process Firefox to users with a select set of well tested extensions.
Those users have been enjoying the 400% increase in responsiveness and a 700% improvement when web pages are loading. That included almost every Firefox user not using extensions. Shortly after the carefully measured roll-out, we increased to approximately 50% of our user base. About four months ago, we launched multi-process Firefox to a small group of Firefox 48 users.
0 kommentar(er)
