Skip to content

Trie ChangeSets: Pruning needs to be more aggressive #18950

@mediocregopher

Description

@mediocregopher

Describe the feature

In just a couple of days of running these changes on mainnet both the AccountsTrieChangeSets and StorageTrieChangeSets grew to over 25 GiB. The pruning settings right now will keep up to 10k blocks worth of data, but we really only need up to the finalized block, so it's worthwhile to make pruning more aggressive.

Additional context

No response

Metadata

Metadata

Labels

A-pruningRelated to pruning or full nodeA-trieRelated to Merkle Patricia Trie implementationC-enhancementNew feature or request

Type

No type

Projects

Status

Completed

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions