3 ms·
These points also apply to HTTP, except (5). In fact, resource usage is my biggest problem with IPFS at the moment; and the reason I turned off my node :(
by chriswarbo 4y ago
These points also apply to HTTP, except (5). In fact, resource usage is my biggest problem with IPFS at the moment; and the reason I turned off my node :(
- hecturchi 4y agoIt is relatively new so not many people know about it, but now libp2p (and Kubu/go-ipfs) can be configured with a Resource Manager that effectively can keep a lot of the resource usage at bay: https://github.com/ipfs/kubo/blob/master/docs/config.md#swarmresourcemgr https://github.com/ipfs/kubo/blob/master/docs/config.md#swar...
- noasaservice 4y agoYeah, you really can't get away from the chattiness of IPFS because that's just how distributed hash tables work. But the CPU and RAM costs... well, those are frankly exorbitant to what amounts to a glorified Apache web server bolted on with a Bittorrent tracker.
- pclmulqdq 4y agoThe CPU and RAM costs are all about figuring out how to pay people (and charge them) algorithmically. I remember private trackers that had seeding and uptime requirements (enforced by people) 20 years ago.
- chriswarbo 4y ago> The CPU and RAM costs are all about figuring out how to pay people (and charge them) algorithmically This sounds more like Filecoin than a normal IPFS node. I've never used Filecoin, I just host my static Web sites and git mirrors on IPFS, but the de facto Go implementation of IPFS slows down my laptop noticably and is consistently the highest consumer of RAM.