3 ms·
No, but getting lower latency javascript with tab-level independent parallelism makes a lot more CPU available. Firefox simply runs all javascript in one physi
by blasdel 16y ago
No, but getting lower latency javascript with tab-level independent parallelism makes a lot more CPU available.
Firefox simply runs all javascript in one physical thread, so it can only ever use about 100% CPU, while Chrome can use N00% CPU.
- jamesaguilar 16y agoIf the same amount of overall work is getting done, that shouldn't matter. At any rate, these wakeups will be when chrome is idle in the background, so I doubt it will be using more than one whole CPU.