Badger -> Pebble DB M2 - DB access refactoring for low-risk data (AN, EN, VN) #6527
Open
14 of 18 tasks
Labels
Execution
Cadence Execution Team
Why
For top-level overview see Epic: #6515
Specifically for this issue:
Subset of Execution data gets indexed on ANs (events, Txs, Tx results, collections (meta object on top of Tx) ⇒ data that gets pulled out of execution data blobs).
ANs are the biggest data-heavy node after EN, expecting to grow further with EVM equivalence. By enabling data pruning we enable them to run AN with index on lower spec HW.
Most of this work is also relevant for VNs and because VNs are stateless we can cover it in this milestone as there is low risk of unintended consequences of DB operations.
Current status
How will we measure success ?
DACI
Tasks
Execution
Verification
Access
Tools
The text was updated successfully, but these errors were encountered: