[SERVER-71037] Investigate remaining sort regressions Created: 02/Nov/22  Updated: 29/Oct/23  Resolved: 14/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Mihai Andrei Assignee: Ian Boros
Resolution: Fixed Votes: 0
Labels: pm2697-63, pm2697-m3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes SERVER-75022 Coverity analysis defect 135418: Inco... Closed
causes SERVER-75023 Coverity analysis defect 135430: Inco... Closed
Related
related to SERVER-72856 Investigate sort regressions Closed
Assigned Teams:
Query Execution
Backwards Compatibility: Fully Compatible
Sprint: QE 2023-02-06, QE 2023-02-20, QE 2023-03-06, QE 2023-03-20
Participants:
Linked BF Score: 100
Story Points: 10

 Description   

There are still some outstanding sort regressions that need investigating:

Aggregation.SortLimitHundredCollection100K_1PathKey3Components -17.85888569
Aggregation.SortLimitHundredCollection100K_2KeyCommonPrefix -50.78947141
Aggregation.SortLimitHundredCollection10K_1PathKey3Components -17.97599223
Aggregation.SortLimitHundredCollection10K_2KeyCommonPrefix -50.12421764
Aggregation.SortLimitHundredCollection1K_1PathKey3Components -17.2209994
Aggregation.SortLimitHundredCollection1K_2KeyCommonPrefix -43.20764711
Aggregation.SortLimitOneCollection100K_1PathKey3Components -17.88072416
Aggregation.SortLimitOneCollection100K_2KeyCommonPrefix -51.24985678
Aggregation.SortLimitOneCollection10K_1PathKey3Components -17.26360662
Aggregation.SortLimitOneCollection10K_2KeyCommonPrefix -51.22353458
Aggregation.SortLimitOneCollection1K_1PathKey3Components -17.16735007
Aggregation.SortLimitOneCollection1K_2KeyCommonPrefix -46.598606
Aggregation.SortNoLimitCollection100K_1Key -21.04171993
Aggregation.SortNoLimitCollection100K_1PathKey3Components -24.17484036
Aggregation.SortNoLimitCollection100K_2KeyCommonPrefix -24.64707999
Aggregation.SortNoLimitCollection10K_1PathKey3Components -12.54906047
Aggregation.SortNoLimitCollection10K_2KeyCommonPrefix -29.0405377
Aggregation.SortNoLimitCollection1K_2KeyCommonPrefix -30.5374333
Queries.SortLimitHundredCollection100K_2KeyCommonPrefix
Queries.SortLimitHundredCollection10K_2KeyCommonPrefix
Queries.SortLimitHundredCollection1K_1PathKey3Components
Queries.SortLimitHundredCollection1K_2KeyCommonPrefix
Queries.SortLimitOneCollection100K_2KeyCommonPrefix
Queries.SortLimitOneCollection10K_2KeyCommonPrefix
Queries.SortLimitOneCollection1K_2KeyCommonPrefix
Queries.SortNoLimitCollection100K_1Key
Queries.SortNoLimitCollection100K_1PathKey3Components
Queries.SortNoLimitCollection100K_2KeyCommonPrefix
Queries.SortNoLimitCollection10K_1PathKey3Components
Queries.SortNoLimitCollection10K_2KeyCommonPrefix
Queries.SortNoLimitCollection1K_2KeyCommonPrefix

this ticket tracks the work to investigate them and figure out what to do (if anything at all)



 Comments   
Comment by Githook User [ 10/Mar/23 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'borosaurus'}

Message: SERVER-71037 SBE top-k sort improvements
Branch: master
https://github.com/mongodb/mongo/commit/3ff59aaf07bcc3e44de3bdd6a4d7b8be6b4f115e

Generated at Thu Feb 08 06:17:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.