3 ms·
All browsers use multiple threads internally so single process browsers too can use mutliple cores and, in fact, can more efficiently. Further, most popular mo
by RandyRanderson 9y ago
All browsers use multiple threads internally so single process browsers too can use mutliple cores and, in fact, can more efficiently.
Further, most popular modern operating systems handle processes and threads similarly internally.
I'm not sure what you mean by 60 fps. 2d apps typically don't have render loops as games do - they only "composit" graphics typically by updating the UI only if a section needs to be re-drawn.
- 1123581321 9y agoI am sure you are right, but Mozilla says FF used one process, currently uses two (one for UI, one for content) and the final version of multiprocess will use more for web content and extensions. https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox https://developer.mozilla.org/en-US/Firefox/Multiprocess_Fir... I shouldn't have said 60fps. I just meant low or no interface lag. Regardless of what the system is trying to do internally, Firefox has performance issues in the UI, so hopefully they can address those.