cockroachdb / cockroachdb/pebble
DB size and database sharding
Open
A-storage
T-storage
- Dominant language
- Go
- Stars
- 6k
- Forks
- 584
- Avg merge
- 16h 35m
- Merged PRs (30d)
- 5
Description
Hi guys, we are also using PebbleDB, the data scale is 19.5B KV number, and the storage occupies 1.4TB.
I would like to ask a question, for pebbledb or similar LSM-tree DB, what size of storage can be efficiently read and written? Do you have any experience? At what scale is sharding better than a single database?
Jira issue: PEBBLE-1103
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.