[COMPASS-6351] Investigate changes in PM-3050: Time Series Query Performance Optimizations Created: 06/Dec/22 Updated: 24/Jan/23 Resolved: 24/Jan/23 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Investigation | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Epic Link: | COMPASS-5986 | ||||
| Documentation Changes: | Not Needed | ||||
| Description |
|
Original Downstream Change Summary The explain output of a pipeline containing $_internalUnpackBucket and $group has been changed due to optimization. Description of Linked TicketEpic Summary SummaryImplement in the classic Engine selected optimizations recommended by the Time-Series Query Performance Improvements Spike project. MotivationTIme Series query performance has not lived up to expectations, leading to dissatisfied customers and lost opportunities.
Query team has completed a prior Spike to investigate different approaches to optimize Time Series query performance. This project is a continuation of that work, with the aim of implementing the recommended solutions in production.
Due to the existing feature and performance gap in SBE, we have decided to implement these optimizations first in the classic engine, in order to deliver the gains confirmed in the Spike project.
This is part of the wider Time Series Initiative. Documentation |
| Comments |
| Comment by Maurizio Casimirri [ 24/Jan/23 ] |
|
No Impact for DevTools |