[DOCS-13668] Investigate changes in SERVER-40755: Expose statistics which indicate how many collection scans have executed Created: 26/May/20 Updated: 13/Nov/23 Resolved: 05/Jun/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | John Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 3 years, 35 weeks, 5 days ago | ||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||
| Description |
DescriptionDownstream Change Summary The number of tailable and non-tailable collection scans are now reported in the metrics.queryExecutor.collectionScans section of serverStatus output:
These stats can also be retrieved on a per-collection basis using the queryExecStats option to the $collStats aggregation stage:
Description of Linked TicketIt is unclear how prevalent are data scans. Having statistics on collection and index scans would allow us to decided if improvements in this area are critical for the overall performance. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 05/Jun/20 ] |
|
Author: {'name': 'John Williams', 'email': 'john.williams@10gen.com', 'username': 'jwilliams-mongo'}Message: |
| Comment by John Williams [ 05/Jun/20 ] |
| Comment by John Williams [ 03/Jun/20 ] |