[SERVER-7067] change timing for 'dur' so it doesn't include timing for recordStats; potentially slowing down serverStatus Created: 18/Sep/12 Updated: 30/Sep/16 Resolved: 30/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Barrie Segal | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
It seems that the code to generate "dur" is unchanged for 2.2.0, but the timing for "dur" includes the timing for recordStats, which is new. See dbcommands.cpp around line 651. suggestion: the timeBuilder for "after dur" should be done right after the "dur" section, and a separate timeBuilder should be done after recordStats. Since it is currently lumping both times together but calling it "dur" |