Move pieces of the Stack into WebWorkers

[daviddias]

Tools such as https://github.com/developit/workerize-loader and https://github.com/developit/workerize can make testing WebWorkers processing much simpler and enable us to understand which parts of IPFS could/should be moved into WebWorkers to save processing time.

Ideas that come to mind are the Bitswap Decision Engine, Unixfs-Engine and any Encryption done in JS land.

[daviddias]

Another module to look at https://github.com/developit/greenlet

[victorb]

Tasklets seems useful as well: https://github.com/GoogleChromeLabs/tasklets

[daviddias]

@achingbrain @mcollina any experiencing on using a pattern like this to make things faster?

[mcollina]

I would recommend to generate the certificate in a worker in the browser, as it's a CPU intensive actions that would run for several seconds (unless we can speed it up).

Consider the type of load I've seen from ipfs so far, I don't think there will be any benefit to move part of the flow to a webworker: data needs to be marshalled in/out, and most of the single I/O activity is quite small (there is just a lot of that). What would be of extreme interest is to move all of ipfs into a WebWorker. I would propose to write another module that matches the same public API of ipfs (or a subset), but it runs all the operations in a WebWorker.

[whizzzkid]

js-ipfs is being deprecated in favor of Helia. You can follow the migration plan here #4336 and read the migration guide.

This issue has been resolved in Helia! if this does not address your concern please let us know by reopening this issue before 2023-06-05!