4 ms·

The premise seems to be that IPFS takes too many resources because of DHT, and DHT takes too many resources because it opens too many connections. Possibly a s

The premise seems to be that IPFS takes too many resources because of DHT, and DHT takes too many resources because it opens too many connections. Possibly a single setting needs to be tuned based on a discovered connection thruput? If the entire and sole argument is that is opens too many connections, well, you know, just open fewer connections. This isn't a valid complaint about BitTorrent (in which every client allows for max connection tuning and good clients tune connection making behavior dynamically), and it's not a valid complaint against IPFS in general, just the current state of the code.

hecturchi 5y ago
There is a connection manager (that kills connections when they go over a limit), and I think there is a connection rate limiter that limits how many connections are initiated. Some connections are protected (those manually initiated, or those that are being used to transfer some data etc). It is however true heavier IPFS usage results in more resources used, or slower experience in general. It is also true that the connection manager could be improved to be more expedient in handling spikes.