erigontech / erigontech/erigon
PageLevelCompression for History: database part
Open
ErigonDB
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 1.5k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 455
Description
We implemented PageLevelCompression for History - for files. but not for db.
CommitmentHistory had 10x compression-ratio.
But i'm not sure - is it possible to implement it for DB values or not. DB values table format: `key+txnNum -> oldValue` - maybe not easy to point 16 such keys to 1 compressed multi-value... maybe easy...
Contributor guide
Assessment
This issue has not been assessed yet.