[SERVER-60549] Don't time count() at profile level 0 Created: 07/Oct/21 Updated: 31/Jan/22 Resolved: 31/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Percy | Assignee: | David Percy |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | quick-tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
I noticed ~ScopedTimer showing up in a call-stack profile for the count command. It looks like this timer is supposed to only be used for explain, and query profiling, so we don't need it in a typical case. |
| Comments |
| Comment by David Percy [ 31/Jan/22 ] |
|
I didn't end up seeing any improvement from this, on a patch build. |