Hi so i’m currently playing around with js-ipfs in node trying to understand all the different parts. What i would like to do is limit the bandwidth of data my node provides to each individual peer based on a list. Is that currently doable or are there any examples i can check out?

Just letting you know the GO implementation has the same issue. For some reason the IPFS developers consider this either low priority or unsolvable. It’s a deal-breaker for me and I cannot use IPFS until this issue is fixed. I think a huge number of developers attempting to use IPFS are also driven…

I did all my searching around go-ipfs, and here are some links: [image] JS-IPFS limit bandwidth per peer Coding Is there an issue tracking this? I couldn’t find any on github.com/ipfs/js-ipfs . Implement bandwidth limiting …

I’m reviving this topic, as it seems to be a show stopper with regard to UX. I captured this bandwidth issue in a YouTube video, showing exactly what the issue is and why it’s so detrimental to front end UX: https://youtu.be/f88mTVXsj6I Solutions I’ve tried: Limit the connections by setting Low…

Have you verified your routing is in “dhtclient” mode? The “lowpower” option should turn that on, but maybe you can add it manually also (i.e. specify ‘dhtclient’ as the routing option). Also “lowpower” has no dash in it right? Here’s the profiles list (hopefully up to date) ipfs/go-ipfs/b…

Yes, I’m using the ‘low power’ profile. In this thread @hsn10 indicated that js-ipfs does not have DHT implemented yet. For reference, here is the IPFS config settings for the node at chat.fullstack.cash (the app in the YouTube video). And here is the code that sets it . IPFS node configuration: { …

I guess you’re saying since the JS impl doesn’t have DHT implemented you can’t put “dhtclient” as your Routing Type. I dont’ know much about the rest of those settings so I’m out of ideas. :frowning:

It does look like js-ipfs can use dhtclient routing, according to these release notes for v0.48.0 . However, switching it to Routing.Type: dhtclient does not seem to have an effect, or if anything, is actually making the bandwidth consumption higher.

I also added the libp2p configuration, and I confirmed the configuration for libp2p at runtime. It still doesn’t seem to make a difference to the bandwidth usage. const node = await IPFS.create({ libp2p: { config: { dht: { enabled: true, clientMode: true, }, },…

So when you programatically stop just that one ‘node’ you got back from the ‘IPFS.create’ call you can confirm that the network use goes away? You stated that, already, but I’m just being sure you’ve totally eliminated possibility of some OTHER instance/processing being the culprit. also maybe som…

JS-IPFS limit bandwidth per peer

Help

Akita April 20, 2019, 1:19pm 3

Is there an issue tracking this? I couldn’t find any on github.com/ipfs/js-ipfs .

Topic		Replies	Views
Limit Bandwith of IPFS \| Nodejs Ecosystem and Usage	2	2074	April 20, 2019
How can I can create IPFS node with bandwidth limit controls PER FILE?	0	177	March 22, 2023
Banned by internet provider for running private IPFS gateway Kubo go-ipfs	18	2119	November 28, 2019
High Bandwidth and CPU usage from go-ipfs Help go-ipfs	20	2428	May 29, 2022
My hosting warn me because of IPFS network behavior Kubo	5	1160	November 30, 2018

JS-IPFS limit bandwidth per peer

Related topics