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.

Sign up for GitHub

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

Jump to bottom

Investigate gossipsub SeenCache size between v0.37.0 vs v0.36.0 #4083

Closed
twoeths opened this issue May 30, 2022 · 1 comment
Closed

Investigate gossipsub SeenCache size between v0.37.0 vs v0.36.0 #4083

twoeths opened this issue May 30, 2022 · 1 comment
Assignees
@twoeths
Labels
prio-high Resolve issues as soon as possible.
Milestone
Sprint: July 15, ...

Comments

@twoeths
Copy link
Contributor

twoeths commented May 30, 2022

The size of multiple Gossipsub cache data structures has increased. The biggest is seenCache. Can this be related to decreasing the heartbeat interval?

Screenshot from 2022-05-30 11-06-00

Originally posted by @dapplion in #4074 (comment)
@dapplion dapplion added the prio-high Resolve issues as soon as possible. label Jun 29, 2022
@philknows philknows added this to the Sprint July 15 milestone Jun 29, 2022
@twoeths
Copy link
Contributor Author

twoeths commented Jul 14, 2022

this is due to this PR https://github.com/ChainSafe/lodestar/pull/4011/files in release 0.37, we have to modify gossipsub params according to consensus specs.

For seen cache, by default TTL is 2 minutes, we changed it to 6.4 minutes (550 heartbeats, 0.7s each). The metrics also show ~3x in terms of seen cache size so this is working as expected 👍

@twoeths twoeths closed this as completed Jul 14, 2022
Repository owner moved this from Todo to Done in Lodestar Sprint Planning Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@twoeths twoeths

Labels
prio-high Resolve issues as soon as possible.
Projects
No open projects
Lodestar Sprint Planning
Archived in project
Milestone
Sprint: July 15, 2022
Development

No branches or pull requests
3 participants
@twoeths @dapplion @philknows