-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increased Bandwidth Usage Since dencun Upgrade #1342
Comments
Yes, I found the same problem on my production environment.After the 3.13 upgrade, the P2P traffic is almost doubled, resulting in severe packet loss. The performance of ssv is also much lower than before. |
same problem. any feedback? |
Thanks for letting us know, we're investigating this right now. @haoei Can you please confirm that its solely the SSV node that is causing all of this traffic (70Mbit/s), and it's not a combined traffic of, for example, the SSV + CL + EL nodes together? This is at least an order of magnitude above what we've seen so far. @hwhe @lilkk-jerry Can you please provide the network usage of one of your SSV nodes? We have an upcoming upgrade planned that would reduce traffic tremendously. With that said, we're now brainstorming what can be done in the short-term. |
you use iftop, can clearly see that more than 90% of the traffic is occupied by the ssv p2p port. very obvious。 ecs-8416:13001 <=> 18.237.5.4:13021 106MB 304Kb 2.27Mb 1.89Mb TX: cum: 369MB peak: 25.3Mb rates: 930Kb 7.92Mb 6.42Mb |
@moshe-blox |
Describe the bug
Since the recent upgrade of dencun, I have noticed a significant increase in bandwidth usage for the ssv-node program I am running. The bandwidth peaks at 70Mbit/s, with the majority being consumed by the 13001 p2p port.
To Reproduce
Use iftop -P to observe bandwidth usage. Wait for a while and check the total peak.
Expected behavior
I expect the bandwidth usage to be at the previous level, rather than the current 70Mbit/s.
Node (please complete the following information):
Additional context
I have already tried restarting the program and the system, but the issue persists.
The text was updated successfully, but these errors were encountered: