High CPU when publishing files with js-ipfs

[ido-ran]

• Version: js-ipfs/0.27.5
• Platform: macOS High Sierra 10.13.2 (17C205)
• Subsystem: Chrome Version 63.0.3239.132 (Official Build) (64-bit)

Type: Bug

Severity: Medium

Description:

I'm building a system in which js-ipfs node publish file and go-ipfs node get it, I'm using out-of-bound means to notify the content hash.
I've noticed that after a few seconds of fetching the file by go-ipfs the js-ipfs app in Chrome browser starts to have very high CPU usage between 50-100%.

Steps to reproduce the error:

Use webpack example app to publish a file (photo is easiest usually) and use gateway.ipfs.io it get it.

I've record a Chrome Performance session you can use to see the high CPU.

[daviddias]

Hi @ido-ran. Thanks for the report. This is a known "situation", we need to get better and perf and benchmarking to make sure that we don't waste unnecessary resources. Unfortunately, the Browser is a really limited environment and so we need to be super careful.

[whizzzkid]

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

Please feel to reopen with any comments before 2023-06-05. We will do a final pass on reopened issues afterward (see #4336).