Note: There was a minor change to the setup to give each page a unique domain. I load the first 30 pages of the tp5 page set (a snapshot of Alexa top 100 websites from a few years ago), each in its own tab, with 10 seconds in between loads and 60 seconds of settle time at the end. This bodes well for the e10s-multi project. Overall I feel solid about these numbers, especially considering where we were just a year ago. Making sure we have measurements now is important it’s good to know where we can improve. These need to be taken into consideration when choosing how many content processes to enable and pushing to eight doesn’t give us much breathing room. We already have or are adding additional processes such as the plugin process for Flash and the GPU process. As you can see we actually do pretty well, but I don’t think it’s realistic to ship with that many nor do we currently plan to. I included Firefox with eight content processes to keep us honest.
CHROME VS SAFARI MAC 2017 MAC
Surprisingly on Mac Firefox is better than Safari with two content processes, compared with last year where we used 2X the memory with just one process, now we’re on par with four content processes.
This is pretty impressive given last year we were in the same position with one content process. Two content processes is still better than IE, with four we’re a bit worse. Our current plan is to only move up to four content processes, so this is great news.
CHROME VS SAFARI MAC 2017 WINDOWS
We can see that Firefox with four content processes fares better than Chrome on all platforms which is reassuring Chrome is still about 2X worse on Windows and Linux. A year later let’s see how Firefox fares on Windows, Linux, and OSX with multiple content processes enabled.
0 kommentar(er)
