Skip to content
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

Performance issue when there are too many mesh peers #5420

Closed
twoeths opened this issue Apr 26, 2023 · 1 comment
Closed

Performance issue when there are too many mesh peers #5420

twoeths opened this issue Apr 26, 2023 · 1 comment
Labels
scope-networking All issues related to networking, gossip, and libp2p. scope-performance Performance issue and ideas to improve performance.

Comments

@twoeths
Copy link
Contributor

twoeths commented Apr 26, 2023

Describe the bug

Right now mesh peer param Dhigh=12, there could be too many mesh peers per subnet on a test mainnet node

Screenshot 2023-04-26 at 09 12 03

Gossip Block process time

Screenshot 2023-04-26 at 09 16 11

Gossip Block Received Delay

Screenshot 2023-04-26 at 09 24 22

If we configure network.gossipsubDHigh=9 so that there is no subnet has more than 9 mesh peers

Screenshot 2023-04-26 at 09 18 17

we got better metric

Screenshot 2023-04-26 at 09 19 56

Screenshot 2023-04-26 at 09 24 42

Expected behavior

Lodestar should able to handle high number of mesh peers per spec (with Dhigh=12)

@philknows philknows added scope-networking All issues related to networking, gossip, and libp2p. scope-performance Performance issue and ideas to improve performance. labels Apr 28, 2023
@twoeths
Copy link
Contributor Author

twoeths commented Aug 20, 2023

gossipsubDHigh was set back to 12, closing the issue

@twoeths twoeths closed this as completed Aug 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope-networking All issues related to networking, gossip, and libp2p. scope-performance Performance issue and ideas to improve performance.
Projects
None yet
Development

No branches or pull requests

2 participants