prometheus / prometheus/prometheus
tsdb: Investigate Postings Compression
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 66.1k
- Forks
- 10.8k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 131
Description
We have large postings lists stored that are intersected for every single query, we can do better in terms of compression and intersection.
BP-128 is a good candidate with a Golang implementation. The issue here is that a native golang implementation doesn't exist and that means it doesn't work on ARM and other architectures.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by locating the TSDB postings-list implementation. Read the linked BP-128 paper and Dgraph Go implementation, then assess compression, intersection performance, and support for ARM and other architectures. Done should be a documented recommendation or implementation direction with relevant benchmarks and constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100