Skip to content

Persistent memory growth when using the priority mempool #8775

@creachadair

Description

@creachadair

When running a testnet against Tendermint v0.35, the Vega team observed that enabling the new priority mempool feature triggered unexpected memory growth in their nodes as compared to using the legacy (sequential) mempool on a similar workload. In summary, a validator with a 10K mempool with a 2K cache shows moderate growth on a resident heap of between 500MiB and 1GiB using the sequential mempool, but quickly rose to 3GiB (which ran over cap and terminated the process) when using the priority mempool.

Metadata

Metadata

Assignees

No one assigned

    Labels

    C:mempoolComponent: MempoolT:bugType Bug (Confirmed)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions