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

fix: reduce merkle clean_threshold to 5000 #7364

Merged
merged 1 commit into from Apr 2, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion book/run/config.md
Expand Up @@ -179,7 +179,7 @@ The merkle stage uses the indexes built in the hashing stages (storage and accou
# The threshold in number of blocks before the stage starts from scratch
# and re-computes the state root, discarding the trie that has already been built,
# as opposed to incrementally updating the trie.
clean_threshold = 50000
clean_threshold = 5000
```

### `transaction_lookup`
Expand Down
2 changes: 1 addition & 1 deletion crates/config/src/config.rs
Expand Up @@ -222,7 +222,7 @@ pub struct MerkleConfig {

impl Default for MerkleConfig {
fn default() -> Self {
Self { clean_threshold: 50_000 }
Self { clean_threshold: 5_000 }
}
}

Expand Down
2 changes: 1 addition & 1 deletion crates/stages/src/stages/merkle.rs
Expand Up @@ -21,7 +21,7 @@ use tracing::*;

/// The default threshold (in number of blocks) for switching from incremental trie building
/// of changes to whole rebuild.
pub const MERKLE_STAGE_DEFAULT_CLEAN_THRESHOLD: u64 = 50_000;
pub const MERKLE_STAGE_DEFAULT_CLEAN_THRESHOLD: u64 = 5_000;

/// The merkle hashing stage uses input from
/// [`AccountHashingStage`][crate::stages::AccountHashingStage] and
Expand Down