Skip to content

Memory leak regression #7130

@LesnyRumcajs

Description

@LesnyRumcajs

Summary

Our recent performance improvements are very impressive, but we might have gone too fast too furious.

Image

My node also OOMed over the weekend, logs shared internally. This is a blocker for the next release.

We already identified a couple of candidates for this, this is more for tracking purposes.

Completion Criteria

  • Ensure memory usage is bounded - by default the node must not go above 16 GiB with all the caches etc.
  • Ensure cache metrics are correct.

Additional Links & Resources

Metadata

Metadata

Assignees

Labels

Type: TaskDiscrete task to implement

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions