cockroachdb / cockroachdb/pebble
db: consider avoiding O(L0 file count) range key iterator construction
Open
A-storage
C-performance
T-storage
- Dominant language
- Go
- Stars
- 6k
- Forks
- 584
- Avg merge
- 16h 35m
- Merged PRs (30d)
- 5
Description
Creating a range key iterator must iterate through all the files within L0. We have a couple options for addressing this:
https://github.com/cockroachdb/pebble/pull/3004#pullrequestreview-1690334803
Jira issue: PEBBLE-69
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the discussion in cockroachdb/pebble#3004, especially the linked pull-request review, and then trace how range key iterator construction examines L0 files. The issue is done only when an agreed approach avoids the current O(L0 file count) construction cost, but no implementation files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100