[SERVER-666] query optimizer introspection Created: 23/Feb/10 Updated: 02/Sep/22 Resolved: 22/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 5 |
| Labels: | query_triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Linked BF Score: | 35 | ||||||||||||||||||||||||||||||||
| Description |
|
Now have tools to see all plans, etc... |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 22/Jan/14 ] |
|
I think what we've done qualifies, didn't need to do the original description. |
| Comment by hari.khalsa@10gen.com [ 22/Jan/14 ] |
|
All the information is available via other methods (profiling, verboseQueryLogging, query plan cache commands). We don't know if we want to log into a special collection yet. |