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

Track down high memory usage #1338

Closed
rkeene opened this issue Oct 30, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@rkeene
Copy link
Contributor

commented Oct 30, 2018

Surrounding epoch block rollout there were reports of excessive memory usage on the node

@rkeene rkeene added bug major labels Oct 30, 2018

@rkeene rkeene added this to the V17.0 milestone Oct 30, 2018

@rkeene

This comment has been minimized.

Copy link
Contributor Author

commented Dec 14, 2018

This was tracked down almost entirely to connection tracking functions being generated, fixed in #1444.

There were a few other causes, but they have also been addressed at this point.

@rkeene rkeene closed this Dec 14, 2018

@rkeene

This comment has been minimized.

Copy link
Contributor Author

commented Dec 19, 2018

Post-release analysis of high memory usage:

  • Excess anonymous functions/lambdas created, specifically faster than they could be acted on. Resolution: Fixed in #1444
  • Unbounded bootstrapping process that could download state blocks to memory. Resolution: Fixed in #1448
  • Vote and Block deduplicator (uniquer) never cleaned up cached copies of votes or blocks. Resolution: Fixed in #1473
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.