-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Open
6 / 96 of 9 issues completedLabels
C-enhancementNew feature or requestNew feature or requestC-perfA change motivated by improving speed, memory usage or disk footprintA change motivated by improving speed, memory usage or disk footprintC-tracking-issueAn issue that collects information about a broad development initiativeAn issue that collects information about a broad development initiative
Description
Describe the feature
reth does not currently function well without some kind of wait time between nP+FCU calls. During our own benching we generally use something like 400ms, but ideally we eliminate this requirement.
When run without any wait time between blocks, we see blocks pile up in memory faster than they get flushed to disk. This is almost certainly a bug which needs to be fixed, as without doing so reth becomes unusable.
There are other improvements we can make in this area as well:
- There are some low-hanging persistence optimizations which can be made.
- We can investigate increasing number of blocks which are cached in memory.
- Future-proof by benching with larger blocks
Additional context
No response
Reactions are currently unavailable
Sub-issues
Metadata
Metadata
Assignees
Labels
C-enhancementNew feature or requestNew feature or requestC-perfA change motivated by improving speed, memory usage or disk footprintA change motivated by improving speed, memory usage or disk footprintC-tracking-issueAn issue that collects information about a broad development initiativeAn issue that collects information about a broad development initiative
Type
Projects
Status
Backlog