[Feature request] Move (most of) WebTorrent into Web Workers

[jimmywarting]

Using WebTorrent in the main thread makes the page unresponsive sometimes.
What would it take to move WebTorrent into a web worker?

I know WebRTC is not supported in web workers for example.
So you would have to communicate back and forth with postMessage to handle WebRTC.

---

Almost feel we need a performance sprint and focus on making WebTorrent faster and CPU friendlier.
Having some benchmark testing would be awesome too.

[Chocobozzz]

@jimmywarting Did you try this patch?

[jimmywarting]

Nope, not yet. But it looks like that is just one tiny adjustment (and only for Chrome).
Still think it would be more beneficial to have it all in a web worker

[Chocobozzz]

Sure, it was just to know if the patch improved your unresponsive issues. (fyi firefox supports requestIdleCallback too)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.