[SERVER-81206] BSONColumn is decompressed several times during timeseries validation Created: 19/Sep/23 Updated: 06/Feb/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Damian Wasilewicz | Assignee: | Damian Wasilewicz |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | storex-ranked | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
At the moment, we perform BSONColumn decompression several times when running validation with full set to true (or BSONConformance set to true). We perform it once during BSON validation here and then again during timeseries bucket validation here and here. Since this is a relatively expensive operation we can look into re-using the decompressed column from the earlier check in the later checks. |
| Comments |
| Comment by Louis Williams [ 26/Sep/23 ] |
|
We should also add some benchmarks for timeseries validation |