[SERVER-44804] Make tracking of timing information in DocumentSource opt-in Created: 22/Nov/19 Updated: 29/Oct/23 Resolved: 08/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Performance, Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Ian Boros |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | qexec-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Query 2019-12-30, Query 2020-01-13 | ||||||||
| Participants: | |||||||||
| Description |
|
The construction and destruction of ScopedTimer proved to be a noticeable cost when we added stats tracking to agg in For the PlanStage layer, we record statistics to the profiler and include timing information. It appears that we will do this for the find command (and maybe others?) but not for the aggregate command. |
| Comments |
| Comment by Githook User [ 07/Jan/20 ] |
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'puppyofkosh'}Message: |