[SERVER-26518] Include density estimator in geoNear explain output Created: 07/Oct/16 Updated: 28/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Geo, Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | qi-geo, query-skunkworks | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Integration
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
The geoNear query execution stages expend work() cycles inside a process called density estimation. This process is used to compute the size of the successive geoNear search annuli. It is possible for a significant amount of query execution work to be spent inside density estimation, but statistics describing this execution work do not appear inside explain output. We should add stats from density estimation in order to make debugging geoNear easier. |