ipfs daemon has high cpu usage

[bridiver]

Description

The ipfs daemon is using 3-10% cpu continuously (m1 mac laptop) even when not in active use to load content.

Steps to Reproduce

1. Visit an ipfs/ipns url
2. Choose local node
3. Check process stats

Actual result:

High cpu usage

Expected result:

Should have minimal cpu usage when not in active use and ideally shutdown after some period of non-use. @bbondy suggested it could have a pref to always run in the background (default to false)

Reproduces how often:

Easily reproduced

Brave version (brave://version info)

1.40.16

Version/Channel Information:

All channels

• Can you reproduce this issue with the current release? yes
• Can you reproduce this issue with the beta channel? yes
• Can you reproduce this issue with the nightly channel? yes

[cypt4]

@bridiver , on which OS do you see this issue?

[bridiver]

@bridiver , on which OS do you see this issue?

macos m1

[lidel]

By default, Kubo daemon will try to use uPnP and hole punching to become publiclly diallable, and if that is successful it will act as DHT server, accepting DHT PUTs from other peers – this introduces overhead of both CPU and additional bandwidth.

This may get better with each small improvement listed below:

• We are migrating network away from RSA (feat: add warning if daemon uses an RSA peer id ipfs/kubo#9506), which should lower CPU over time.
• update to Kubo 0.17 (Update kubo to 0.17.0 #26996)
  • it ships with ResourceManager enabled by default, and the defaults should help, but also Brave may decide to experiment and adjust limits (docs: Swarm.ResourceMgr)
• switch to universal binaries for macOS
  • done: https://github.com/brave/brave-core-crx-packager/blob/4956d8df401413a58b4833ccf40db7a4332c6794/scripts/packageIpfsDaemon.js#L87-L88
• update to Kubo 0.18
  • It lowers the number of connections that kubo keeps around, which translates to lowered CPU

[Pandapip1]

Is it possible to add an option to disable the daemon while it's not actively being used?

[vadimstruts]

The IPFS local node and scheme has been deprecated