Align storage and deduplication order
Open
- Dominant language
- Go
- Stars
- 11.7k
- Forks
- 802
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 80
Description
Currently our query deduplication requires data to be ordered by `timestamp` and then by `series_id`, while we store the profiles in blocks ordered by `series_id` and then `timestamp`.
We should change the query deduplication to aling those two. It will allow us to keep a lot less allocation during object querying as we don't have open all the profiles rowGroups first before we are able to dedupliate.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.