2 ms·
Chrome is using separate sandboxed processes for the security boundaries, and it actually costs some performance. Tabs get mostly suspended when they're not act
by fulafel 12y ago
Chrome 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.