paradigmxyz/reth - CodSpeed

reth

Blog Docs Changelog

Performance History

Latest Results

also skip shrink_to when cache pruning is disabled Amp-Thread-ID: https://ampcode.com/threads/T-019c3f47-5116-736a-ac71-c1751c06a705 Co-authored-by: Amp <amp@ampcode.com>

alexey/disable-sparse-trie-cache-pruning

26 seconds ago

feat(engine): add --engine.disable-sparse-trie-cache-pruning flag Adds a CLI argument to fully disable sparse trie cache pruning between blocks. When set, the cached sparse trie is preserved without any node pruning or storage trie eviction, keeping the full trie cache intact. This is useful for benchmarking the effects of retaining the full cache vs the default pruning behavior. Amp-Thread-ID: https://ampcode.com/threads/T-019c3f47-5116-736a-ac71-c1751c06a705 Co-authored-by: Amp <amp@ampcode.com>

alexey/disable-sparse-trie-cache-pruning

4 minutes ago

feat(engine): prefetch withdrawal addresses in pre-warming Withdrawals happen at the end of block execution as balance increments. Previously, the pre-warming system did not prefetch any data for these withdrawal addresses, meaning the multiproof computation for withdrawals had to wait for I/O during post-execution. This change generates account-level multiproof prefetch targets for withdrawal addresses and sends them immediately when spawning the payload processor, before transaction prewarming begins. This gives the multiproof task a head start on fetching trie proofs for withdrawal accounts. - Add `withdrawals` field to `ExecutionEnv` - Add `multiproof_targets_from_withdrawals()` helper (supports both legacy and V2 proof targets) - Send `PrefetchProofs` for withdrawals at spawn time in non-BAL path - Filter zero-amount withdrawals and deduplicate addresses - BAL path excluded since BAL should already cover withdrawal touches Co-authored-by: mattsse <matt@paradigm.xyz> Amp-Thread-ID: https://ampcode.com/threads/T-019c3de1-3f1a-75ce-89f6-cc1ff085a42c Co-authored-by: Amp <amp@ampcode.com>

mattsse/prefetch-withdrawals

6 hours ago

chore: add changelog

ci/cargo-rail-selective-testing

8 hours ago

fix: unset RUSTC_WRAPPER in detect jobs cargo-rail needs to run cargo metadata which fails when sccache is not installed but RUSTC_WRAPPER is set

ci/cargo-rail-selective-testing

8 hours ago

fix: scope docs build by using cargo doc directly when scoping

ci/cargo-rail-selective-testing

8 hours ago

ci: use cargo-rail for selective crate testing on PRs On PRs, only test crates affected by the changes (and their transitive dependents) using cargo-rail's graph-aware change detection. Merge queue and main pushes continue to run the full --workspace test suite. - Add .config/rail.toml with infrastructure file patterns - Add detect job using cargo-rail-action to unit.yml, integration.yml, and lint.yml - Test/lint jobs fall back to --workspace when detect is skipped (merge_group/push) or when infrastructure files changed (rebuild-all) - Skip jobs entirely when no crates are affected or only docs changed - Scope clippy and udeps to affected crates on PRs

ci/cargo-rail-selective-testing

8 hours ago

chore: use FullBlockHeader correctly

joohhnnn:FullBlockHeaderVSBlockHeader

9 hours ago

Active Branches

feat(engine): add --engine.disable-sparse-trie-cache-pruning flag

last run

4 minutes ago

0%

feat(engine): prefetch withdrawal addresses in pre-warming

last run

6 hours ago

0%

ci: use cargo-rail for selective crate testing on PRs

last run

8 hours ago

0%

© 2026 CodSpeed Technology

Home Terms Privacy Docs