5 ms·
No mention of node performance? Running your own IPFS node with any non-personal amount of traffic is ROUGH. Poor storage quota support combined with a terrible
by kkielhofner 5y ago
No mention of node performance? Running your own IPFS node with any non-personal amount of traffic is ROUGH. Poor storage quota support combined with a terrible garbage collector that consumes 1000% CPU on my Epyc cores every time it runs…
- kevincox 5y agoYeah, I had to take go-ipfs off my home server because it would grind it to a crawl. Even with attempts to memory limit it is seems that somehow it would constantly thrashy disk cache even when basically idle. The think the core IPFS technology is great. But they really need to settle down with changing the higher level protocols and the go-ipfs implementation is truly a piece of junk.
- hecturchi 5y agoThe upcoming release of go-libp2p (0.18.0) includes a resource manager that promises to improve this by effectively enforcing limits. Also, please re-implement it properly!
- testesttest 5y ago2nd this. I saw lots of packet loss on my gig connection when scraping a few TBs over IPFS. Turned off garbage collection which just deletes the whole cache when you go over a threshold?