[SERVER-84574] Capture additional metrics in query stats and evaluate their performance impact Created: 04/Jan/24 Updated: 05/Jan/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mark Benvenuto | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
There are two additional metrics that stakeholders are interested in:
These are WiredTiger statistics that are from a statistics cursor on the WT session. These will be more costly to gather then other statistics and the performance impact may be too great. Performance will need to be evaluated to see if these can be added while meeting the performance goals. |