Nano-node: Track down high memory usage

Created on 30 Oct 2018  路  2Comments  路  Source: nanocurrency/nano-node

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

bug major release_blocker

Most helpful comment

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

All 2 comments

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.

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
Was this page helpful?
0 / 5 - 0 ratings

Related issues

starrynightglider picture starrynightglider  路  5Comments

zhyatt picture zhyatt  路  4Comments

yousifa picture yousifa  路  5Comments

hskang9 picture hskang9  路  4Comments

henry701 picture henry701  路  5Comments