[SERVER-85920] Remove determineBonsaiEligibility from the hot path of SBE engine Created: 30/Jan/24 Updated: 01/Feb/24 Resolved: 01/Feb/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 8.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Milena Ivanova | Assignee: | Hana Pearlman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Assigned Teams: |
Query Optimization
|
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
When running mongod with internalQueryFrameworkControl=trySbeEngine the server seems to spend unnecessary time in determineBonsaiEligibility function (under getExecutorFind). In the attached flame graph of FindProjectionThreeFields benchmark over a 100-document collection the function takes 3.11% (out of 9.28% for getExecutorFind). For larger collections this is probably a smaller issue, but it looks like unnecessary overhead for small collections queries. |
| Comments |
| Comment by Githook User [ 01/Feb/24 ] |
|
Author: {'name': 'HanaPearlman', 'email': 'hana.pearlman@mongodb.com', 'username': 'HanaPearlman'}Message:
|