-
Notifications
You must be signed in to change notification settings - Fork 780
Open
Labels
P:storage-optimizationPriority: Give operators greater control over storage and storage optimizationPriority: Give operators greater control over storage and storage optimizationbacklogA prioritized task in the team's backlogA prioritized task in the team's backlogstorage
Description
Problem definition
Based on the requirements in #63 , we need to evaluate the different database engines in order to find one that satisfies most of them based on a criteria.
Some preliminary work has been done in RFC 001 and insights from the community can be found in the comments of tendermint/tendermint#6032.
- Intern project on understanding pruning/compaction of different databases. The benchmarks also analyzed the impact of key order on the access time. The final presentation of the work is found in DB experiments.pdf
DoD
- An RFC containing:
- The different databases evaluated and the reasoning behind their choice.
- An explanation of the methodology of the evaluation.
- Their ranking based on the requirements.
- Recommendation on which database to choose. - Optimize the chosen database based on the requirements established in Storage evaluation baseline: measure and report current storage related behaviour of CometBFT #67 and feedback from users (Define external users and use cases for the CometBFT storage layer #68)
Original issue tendermint/tendermint#9944
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P:storage-optimizationPriority: Give operators greater control over storage and storage optimizationPriority: Give operators greater control over storage and storage optimizationbacklogA prioritized task in the team's backlogA prioritized task in the team's backlogstorage