3 ms·

Didn't test (yet), but if they do, then what's the point of throttling background tabs?

• simcop2387 6y ago
  Service workers have restrictions on what they can do. They can't interact with thr dom and a few other things to keep them from causing rendering or other changes.
• chhamilton 6y ago
  (Chromium dev here.) We don't throttle workers (that could change, but we don't have firm plans here yet). All things being equal, if you move complex work to workers we're happy because it frees up the main thread to handle input events, compositing, etc. Just because your tab is in the background doesn't mean your renderer process isn't sharing a main thread with a tab that is in the foreground, so in this case it can improve foreground tab performance. Also, spreading a fixed amount of work across more cores and fewer wake-ups is actually more efficient from a power point of view (assuming the wake-ups are synchronized).