3 ms·
Yeah its not quite there yet, but I included them because e.g. in Chrome we have web workers, separate processes for plugins, a separate renderer process, separ
by MrBuddyCasino 12y ago
Yeah its not quite there yet, but I included them because e.g. in Chrome we have web workers, separate processes for plugins, a separate renderer process, separate processes for tabs etc., and multithreading via NaCL.
Maybe a corner case.
- fulafel 12y agoChrome is using separate sandboxed processes for the security boundaries, and it actually costs some performance. Tabs get mostly suspended when they're not active. This is really the gist of the parallelism problem: it only helps when applied to the bottlenecks. Browsers aren't really using it to layout single pages faster, or running JS faster. Yeah, there's some work on parallelism in rendering and GC in production browsers too but it's so far nibbling at the edges. Long way to go to get even 2x speedup compared to single core.