High network usage about go-libp2p HOT 10 CLOSED

Can you post the gossipsub-related question in the gossipsub repo please? And please let me know what insights you get from the BandwidthReporter.

from go-libp2p.

I don't think it has anything to do with the DHT. In any case, you can make your own DHT network and have only the traffic that it is necessary for you and your users.

from go-libp2p.

Is this internet traffic or does it include local network (e.g. mDNS) traffic?

from go-libp2p.

There is no mDNS enabled at those servers (off by default).

from go-libp2p.

Can you try enabling the bandwidth counter: https://github.com/libp2p/go-libp2p/blob/master/core/metrics/bandwidth.go? It's accessible via the libp2p.BandwithReporter option, and should allow you to find out which protocol and peer are responsible for the traffic.

from go-libp2p.

Thanks for your suggestion. We were not aware oft this option. We will enable it and will share the result here.

However, we tried to reduce the traffic in the latest release through these modifications:

1. Removing the Signature (64 bytes).
2. Removing the PID author (38 bytes).
3. Defining the Message ID as the first 20 bytes of the message hash.
4. Introducing a new type of node: Node Gossip (experimental).

Node Gossip nodes are a type of node that gossips the message. Meanwhile, non-gossip nodes only consume incoming messages, and they don't broadcast the message. This is experimental, but it appears to be working fine so far.

There are some questions:

1. In certain situations (like block announcements), consensus nodes might produce the exact message with the exact message ID. We assumed that identical messages emitted by different nodes would be ignored by the network, but it seems that this is not the case. We still observe nodes receiving the same message repeatedly. Any thoughts on this?

2. It appears that the node gossip sends messages to all nodes, regardless of whether they have the message or not. Is there any way to reduce outgoing traffic? I'm not sure, but maybe using the WithFloodPublish(false) config could help?

from go-libp2p.

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

from go-libp2p.

Unfortunately, we were unable to install the metrics using BandwidthReporter.
I've been told that it didn't reveal any new information.
We apologize if our efforts couldn't be of assistance in this case.

from go-libp2p.

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

from go-libp2p.

This issue was closed because it is missing author input.

from go-libp2p.