8000 investigate using github.com/google/btree instead of our own · Issue #4420 · cockroachdb/pebble · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

investigate using github.com/google/btree instead of our own #4420

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.

Sign up for GitHub

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

Jump to bottom
Open
RaduBerinde opened this issue Mar 25, 2025 · 2 comments
Open

investigate using github.com/google/btree instead of our own #4420

RaduBerinde opened this issue Mar 25, 2025 · 2 comments
Assignees
@RaduBerinde
Labels
A-storage C-cleanup T-storage

Comments

@RaduBerinde
Copy link
Member
RaduBerinde commented Mar 25, 2025 •
edited by cockroach-jira-scripts
Loading

Investigate if we can just use https://github.com/google/btree instead of our own implementation. It supports lazy cloning.

Jira issue: PEBBLE-360
@RaduBerinde RaduBerinde self-assigned this Mar 25, 2025
@jbowens
Copy link
Collaborator
jbowens commented Mar 25, 2025

One obstacle might be the 'annotations' we cache on btree nodes. Our existing implementation was copied (and pruned) from an implementation within Cockroach, and I don't know the history there.

@petermattis
Copy link
Collaborator

I believe the Cockroach implementation started from the google/btree implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RaduBerinde RaduBerinde

Labels
A-storage C-cleanup T-storage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jbowens @petermattis @RaduBerinde
0