[SERVER-72126] Investigate improvements to bucket reopening query Created: 14/Dec/22 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-storex-namer | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Participants: | |||||
| Description |
|
In some cases, we use a query to determine which time series bucket to reopen for a given incoming measurement. Sometimes there are multiple candidate buckets to choose from, and the decision is somewhat arbitrary. Different choices may lead to larger vs. smaller buckets which could affect cache usage; larger vs. smaller time differences between consecutive measurements which could affect compression ratios; etc. We have some freedom to experiment with this and fine-tune our strategy. |