github/reth
1
1
Fork 0
mirror of https://github.com/paradigmxyz/reth.git synced 2026-01-09 15:28:01 -05:00
Code Issues Packages Projects Releases Wiki Activity

feat(engine): set default_memory_block_buffer_target to zero (#17963)

Browse Source
This commit is contained in:
Femi Bankole
2025-08-20 19:01:00 +01:00
committed by GitHub
parent 8435976563
commit 1ed7450d53
3 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/vocs/docs/pages/cli/reth/node.mdx
View File

@@ -786,7 +786,7 @@ Engine:
--engine.memory-block-buffer-target <MEMORY_BLOCK_BUFFER_TARGET>
Configure the target number of blocks to keep in memory
[default: 2]
[default: 0]
--engine.legacy-state-root
Enable legacy state root

3
docs/vocs/docs/pages/sdk/examples/standalone-components.mdx
View File

@@ -80,9 +80,8 @@ let factory = EthereumNode::provider_factory_builder()
Reth buffers new blocks in memory before persisting them to disk for performance optimization. If your external process needs immediate access to the latest blocks, configure the node to persist blocks immediately:
- `--engine.persistence-threshold 0` - Persists new canonical blocks to disk immediately
- `--engine.memory-block-buffer-target 0` - Disables in-memory block buffering
Use both flags together to ensure external processes can read new blocks without delay.
Using this flag ensures external processes can read new blocks without delay.
As soon as the reth process has persisted the block data, the external reader can read it from the database.