cockroachdb / cockroachdb/pebble
pin index and bloom filter blocks to reader
Open
A-storage
T-storage
- Dominant language
- Go
- Stars
- 6k
- Forks
- 584
- Avg merge
- 16h 35m
- Merged PRs (30d)
- 5
Description
I'm finding that 1%+ of CPU in TPCC (on `c4-standard-32-lssd`) is "loading" bloom filters and index blocks from cache (read lock, value ref counter, map lookup, updating category stats). We should "pin" these blocks inside the sstable reader for (at least) L0-L4.
Jira issue: PEBBLE-1303
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.