With the default settings the ipfs service used about 20% of CPU, stalled my network, and eventually crashed my router. This was reproducible, and none of my hardware is particularly antiquated, just your average desktop set-up. Reporting the issue upstream, apparently this is common enough to warrant them shipping a special config: https://discuss.ipfs.io/t/high-bandwidth-and-cpu-usage-from-ipfs/13982 I am wondering whether this (i.e. `ipfs config profile apply lowpower`) or at least the fact that this software may crash your router shouldn't be mentioned in elog/einfo/ewarn. Reproducible: Always Steps to Reproduce: 1. emerge go-ipfs 2. cd /var/lib/ipfs 3. su -s /bin/sh -c "ipfs init -e" ipfs 4. /etc/init.d/ipfs start 5. wait and be amazed Actual Results: router crashes Expected Results: share and download files
I think a good approach would be to add a USE flag like "lowpower" and a message describing the potential issue. I don't think it should be applied by default though (for the reasons stated in the link).
It turns out that having a USE flag is harder than I thought. Sometimes migration should be done before settings could be apply so it may or may nor work depending on this. For this reason I fallback to print a warning with a suggested workaround
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=de362e13b3af2976bce18b2031cf5b0d5c3c479d commit de362e13b3af2976bce18b2031cf5b0d5c3c479d Author: David Roman <davidroman96@gmail.com> AuthorDate: 2022-06-13 20:10:21 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-06-30 20:23:45 +0000 net-p2p/go-ipfs: add 0.13.0 Closes: https://bugs.gentoo.org/838238 Signed-off-by: David Roman <davidroman96@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/25884 Signed-off-by: Sam James <sam@gentoo.org> net-p2p/go-ipfs/Manifest | 1 + net-p2p/go-ipfs/go-ipfs-0.13.0.ebuild | 69 +++++++++++++++++++++++++++++++++++ 2 files changed, 70 insertions(+)
