[SERVER-81435] Add metrics to capture impact of time series group commit Created: 25/Sep/23 Updated: 19/Jan/24 Resolved: 03/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0, 6.0.12, 7.0.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Dan Larkin-York |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution NAMER
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v7.0, v6.0, v5.0
|
||||||||
| Sprint: | Execution Team 2023-11-13 | ||||||||
| Participants: | |||||||||
| Description |
|
The current metrics the server collects for the time series insert path do not allow us to fully capture how often the group commit feature is utilized. This makes it difficult to understand how important the feature is for the performance of a given workload. Adding metrics around how often the group commit functionality is used (e.g. how many inserts were committed by the inserting thread vs. how many were committed by a different thread) should let us measure this. |
| Comments |
| Comment by Githook User [ 10/Nov/23 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: (cherry picked from commit dd25a9fa1d145ba84ad8fa8f57d0a3bfa6cff511) |
| Comment by Githook User [ 09/Nov/23 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: (cherry picked from commit dd25a9fa1d145ba84ad8fa8f57d0a3bfa6cff511) |
| Comment by Githook User [ 02/Nov/23 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |