There was extensive discussion about how to reduce the data usage on this thread. The data usage was as high as 900GB/month as reported in the discussion. What is average data usage a dhtclient node has with the current ipfs release? Anyone has usage data to share? Many thanks.
There’s no one answer. It depends on what data you’re storing, how much data you’re storing, what data you’re fetching, how many peers you connect to, what your connection manager limits are, etc.
Probably a better phrasing of the question is what is the data usage of overhead to keep a node running. As said, this should not include the actual data download and upload. As I understand, the data usage of node are from announcement and searching (keep connection with peers), bitswap (including acutal data sharing). The more peers a node is connecting to, the more bandwidth/data is consumed. In previous implementation, there is no cap number of peers connected.
Got it. The data usage is mostly from:
- Keeping the DHT routing table up-to-date.
- Receiving/sending address updates as our peer’s addresses change (really low traffic).
- Bitswap requests. This is the vast majority of the traffic.
On my idle dhtclient node, I’m seeing ~20MiB/h, which is ~13.3GiB per month (or ~115Gbits/month, which is usually how bandwidth is charged).
Note: That’s what IPFS is tracking. The OS may see more, and the provider may see even more due to (TCP, security, etc. overhead).