Bug 1315803 Comment 11 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Jens Stutte [:jstutte] from comment #10)
> Hi Andrew, to be more concrete: Do we have a bug we can dupe this on then?

No, we would need to file new bugs.  And this would also entail figuring out what we want our policy to be.  This may be better spun off in favor of a product-level decision/investigation into whether there are cases where we should be throttling workers or the impact of workers.  There's real potential for cross-browser compat issues here.

That said, e10s and Fission help alleviate much of the original concern here.  Specifically:
1. e10s means that workers aren't harming the general responsiveness as the browser as a whole because the parent process's main thread is not interfered with.
2. Fission means thats the performance implications of spammed postMessage on windows should only be meaningfully impact that origin's main thread.
  - That said, for BroadcastChannel (which this patch touched) and MessageChannel (related), those messages still do get routed through the PBackground thread so there is some potential concern there.  But this patch did nothing to address that.
(In reply to Jens Stutte [:jstutte] from comment #10)
> Hi Andrew, to be more concrete: Do we have a bug we can dupe this on then?

No, we would need to file new bugs.  And this would also entail figuring out what we want our policy to be.  This may be better spun off in favor of a product-level decision/investigation into whether there are cases where we should be throttling workers or the impact of workers.  There's real potential for cross-browser compat issues here.

That said, e10s and Fission help alleviate much of the original concern here.  Specifically:
1. e10s means that workers aren't harming the general responsiveness as the browser as a whole because the parent process's main thread is not interfered with.
2. Fission means thats the performance implications of spammed postMessage on windows should only be meaningfully impact that origin's main thread.
   - That said, for BroadcastChannel (which this patch touched) and MessageChannel (related), those messages still do get routed through the PBackground thread so there is some potential concern there.  But this patch did nothing to address that.

Back to Bug 1315803 Comment 11