Confirmed users
95
edits
(minor) |
(updated bug numbers) |
||
Line 24: | Line 24: | ||
** It's really hard to take/get consistent measurements while gmail loads in the bg, due to network latency, gmail load timing, etc. | ** It's really hard to take/get consistent measurements while gmail loads in the bg, due to network latency, gmail load timing, etc. | ||
** Facebook scrolls worse than yahoo/twitter on most configs (except single tab + balanced where the system is fast enough and all pages reach ~60fps) | ** Facebook scrolls worse than yahoo/twitter on most configs (except single tab + balanced where the system is fast enough and all pages reach ~60fps) | ||
** Power saver shows consistently worse results than balanced | ** Bug {{Bugzilla|1213425}} Power saver shows consistently worse results than balanced | ||
** No major differences between win8 and 10 across the board | ** No major differences between win8 and 10 across the board | ||
** No major differences between non-e10s and e10s | ** No major differences between non-e10s and e10s | ||
** Single tab - no major differences between non-e10s/e10s/e10s-multi(3) | ** Single tab - no major differences between non-e10s/e10s/e10s-multi(3) | ||
** Gmail loading in bg - affects most* configurations badly | ** Bug {{Bugzilla|1213413}} Gmail loading in bg - affects most* configurations badly | ||
*** Except e10s-multi(3) which improves performance on this case dramatically | *** Except e10s-multi(3) which improves performance on this case dramatically | ||
Line 57: | Line 57: | ||
** The google image search results scrolls best across configurations (and typically perfectly), yahoo results scroll somewhat worse, and facebook scrolls the worst of these pages. | ** The google image search results scrolls best across configurations (and typically perfectly), yahoo results scroll somewhat worse, and facebook scrolls the worst of these pages. | ||
*** For this reason, it's probably better to use facebook for scroll benchmarks. | *** For this reason, it's probably better to use facebook for scroll benchmarks. | ||
** D2D1_1 scrolls worse than other D2D configs (including no-D2D) on different pages, different GFX configs, and e10s yes/no. | ** Bug {{Bugzilla|1213440}} D2D1_1 scrolls worse than other D2D configs (including no-D2D) on different pages, different GFX configs, and e10s yes/no. | ||
** facebook scrolls quite badly with D3D11-warp and D3D9, especially with e10s. | ** facebook scrolls quite badly with D3D11-warp (bug {{Bugzilla|1213432}}) and D3D9 (bug {{Bugzilla|1213429}}), especially with e10s. | ||
** Except for D2D1_1, D3D11-warp and D3D9, most other configs perform similarly. | ** Except for D2D1_1, D3D11-warp and D3D9, most other configs perform similarly. | ||
** With e10s, the performance differences between gfx configs seem more extreme than without e10s. | ** With e10s, the performance differences between gfx configs seem more extreme than without e10s. | ||
Line 124: | Line 124: | ||
*** Firefox no-e10s is similar to chrome (more than chrome for the "no URL tabs" case) | *** Firefox no-e10s is similar to chrome (more than chrome for the "no URL tabs" case) | ||
*** IE is second with ~60-70% more memory than chrome (less than chrome for the "no URL tabs" case) | *** IE is second with ~60-70% more memory than chrome (less than chrome for the "no URL tabs" case) | ||
*** | *** Bug {{Bugzilla|1213435}} Firefox e10s-multi uses roughly twice the memory which Chrome uses | ||
*** Edge slightly more memory than Firefox e10s-multi (though less than Firefox for the "no URL tabs" case) | |||
** E.g. for 15 tabs: | ** E.g. for 15 tabs: | ||
*** Chrome: 720M, 18 processes | *** Chrome: 720M, 18 processes |