[SERVER-10659] Admin Data for Fragmentation and Index usage Created: 31/Aug/13 Updated: 23/Nov/16 Resolved: 02/Sep/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Performance |
| Affects Version/s: | 2.5.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Brandon Hedge | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | index, stats | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
All |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Please add an admin data structure to track the usage of indexes. The amount of updates, the amount of user reads and other general usage stats. This data structure can be stored in memory and does not need to be persisted to disk. It would also be beneficial to have the ability to report fragmentation of collections and indexes (not contiguous on disk). |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 02/Sep/13 ] |
|
Hi Brandon, We are continuously improving our server statistics. I hope you're familiar with the stats currently available from db.serverStatus. What are the specific statistics you are looking for? Regarding deeper storage statistics, 2.4 released an experimental feature and accompanying visualizer (not recommended to be run on production system) which you can read about here: See and vote up similar tickets in this vein: |