[SERVER-43768] Investigate the slowest sections of ReplSetTest data consistency checks and remove any wasted downtime Created: 02/Oct/19 Updated: 06/Dec/22 Resolved: 13/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | William Schultz (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
Investigate the slowest parts of the consistency checks ReplSetTest.checkReplicatedDataHashes and ReplSetTest.checkOplogs to identify and remove any areas of wasted downtime. Wasted downtime would be any time spent not doing useful, required work. For example, waiting for data to propagate over the network or waiting for an arbitrary timeout to fire in the server e.g. a heartbeat interval or election timeout. |
| Comments |
| Comment by William Schultz (Inactive) [ 13/Dec/19 ] |
|
The potential performance improvements to be had here weren't deemed significant enough, so we are closing this. This is the histogram profile of consistency check durations in the replica_set suite as of this commit: |