8000 Evaluate database engines according to requirements and decide which one to optimize · Issue #64 · cometbft/cometbft · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Evaluate database engines according to requirements and decide which one to optimize #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 of 3 tasks
Tracked by #44 ...
jmalicevic opened this issue Dec 27, 2022 · 2 comments
Open
2 of 3 tasks
Tracked by #44 ...
Labels
backlog A prioritized task in the team's backlog P:storage-optimization Priority: Give operators greater control over storage and storage optimization storage

Comments

@jmalicevic
Copy link
Contributor
jmalicevic commented Dec 27, 2022

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

Original issue tendermint/tendermint#9944

@jmalicevic jmalicevic added storage major-priority A major, long-running priority for the team labels Dec 27, 2022
@jmalicevic jmalicevic self-assigned this Dec 27, 2022
@thanethomson thanethomson removed the major-priority A major, long-running priority for the team label Jan 4, 2023
@thanethomson thanethomson moved this to Todo in CometBFT 2023 Jan 21, 2023
@jmalicevic jmalicevic added this to the 2023-Q2 milestone Mar 27, 2023
@jmalicevic jmalicevic mentioned this issue Jun 27, 2023
21 tasks
@jmalicevic jmalicevic modified the milestones: 2023-Q2, 2023-Q3 Jun 27, 2023
@jmalicevic jmalicevic added the P:storage-optimization Priority: Give operators greater control over storage and storage optimization label Jun 27, 2023
@jmalicevic jmalicevic removed their assignment Jun 27, 2023
@jmalicevic jmalicevic changed the title Evaluate available database engines according to our requirements Evaluate database engines according to requirements and decide which one to tune Jun 27, 2023
@andynog andynog changed the title Evaluate database engines according to requirements and decide which one to tune Evaluate database engines according to requirements and decide which one to optimize Jun 27, 2023
@jmalicevic
Copy link
Contributor Author
jmalicevic commented Oct 16, 2023

Analysis on database backends performed by our intern in the summer of 2023

DB experiments.pdf

@jmalicevic jmalicevic removed this from the 2023-Q3 milestone Oct 16, 2023
@jmalicevic jmalicevic added the backlog A prioritized task in the team's backlog label Oct 16, 2023
@melekes
Copy link
Contributor
melekes commented Sep 19, 2024

relevant https://github.com/smallnest/kvbench

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog A prioritized task in the team's backlog P:storage-optimization Priority: Give operators greater control over storage and storage optimization storage
Projects
No open projects
Status: Todo
Development

No branches or pull requests

3 participants
0