Open etherscoredao opened 5 months ago
I guess your cluster / stack / compose / start command is interesting here as you can limit resources there.
For myself I limited the containers in my swarm because I had no luck doing it with the node's config. I also switched to ipns -> dhtclient to reduce traffic on some nodes. Maybe this also reduces the memory footprint (wild guess).
It seems that, the problem is introduced since 0.28.0, and has been fix in the master branch. So I would revert to 0.27.0 .
@etherscoredao if you're able to try with a custom build try updating to the latest go-libp2p master and seeing if things have improved given the fix here https://github.com/libp2p/go-libp2p/issues/2841
I see this too. Debian Linux - x64
[2657620.399067] Out of memory: Killed process 4187 (ipfs) total-vm:48650700kB, anon-rss:34086188kB, file-rss:0kB, shmem-rss:0kB, UID:1001 pgtables:73548kB oom_score_adj:0
I believe this can be closed after most recent fixes in libp2p/quic
Checklist
Installation method
ipfs-desktop
Version
Config
Description
Hi, memory usage increases endlessly. The ipfs kubo node is installed on a server with:
I use docker stats to monitor the memory usage, here are the current log:
Debugging infos: memory stack: ipfs.stack.tar.gz memory heap: ipfs.heap.tar.gz cpu profile: ipfs.cpuprof.tar.gz
Looks like some goroutines are hanging like:
more infos in the attached memory stack file