[SERVER-81988] Add optimizer metrics to curOp Created: 09/Oct/23 Updated: 15/Dec/23 Resolved: 15/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Misha Tyulenev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | auto-reverted | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | QO 2023-11-13, QO 2023-11-27, QO 2023-12-11, QO 2023-12-25 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 165 | ||||||||||||||||||||
| Description |
|
Class curOp contains data specific for the operation and will add estimatedCost, estimatedCardinality, and the query key (as it is defined in the map - see references). curOp already contains information about whether the plan used a collection scan, as well as executionTime and optimizationTime. This will satisfy the goals form the scope to add the data for the system.profile and explain output. |
| Comments |
| Comment by Githook User [ 14/Dec/23 ] |
|
Author: {'name': 'Misha Tyulenev', 'email': 'misha.tyulenev@mongodb.com', 'username': ''}Message: GitOrigin-RevId: eaf42e087ab9c78dedcb673f377901c0cf8ccf54 |
| Comment by Githook User [ 13/Dec/23 ] |
|
Author: {'name': 'auto-revert-processor', 'email': 'dev-prod-dag@mongodb.com', 'username': ''}Message: Revert " This reverts commit 660706bcf93ada7837894ab31c78813a8f141180. GitOrigin-RevId: 5a1633ab52c7d42ff2bf90857014bb9c38f206a5 |
| Comment by Githook User [ 08/Dec/23 ] |
|
Author: {'name': 'Misha Tyulenev', 'email': 'misha.tyulenev@mongodb.com', 'username': ''}Message: GitOrigin-RevId: 660706bcf93ada7837894ab31c78813a8f141180 |