[SERVER-84819] geo performance issue in 2.7.7 Created: 06/Aug/14 Updated: 12/Jan/24 Resolved: 30/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Rui Zhang (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||
| Description |
|
there are some issue with $geoNear performance with SHA 2cbd9f1d77ce6b25e9957d3121fccb521caf848f |
| Comments |
| Comment by Siyuan Zhou [ 30/Oct/14 ] |
|
With density estimation, most of the cases related this issue should be solved. |
| Comment by Siyuan Zhou [ 06/Aug/14 ] |
|
The labeling in test code seems confusing. It is would be better to name this case "Geo.geoNear.2d.findOne.nearSphere.center" since it's not using 2dsphere index. Also it might be interesting to see the performance with 2dsphere index. |
| Comment by Greg Studer [ 06/Aug/14 ] |
|
Just to clarify for myself and everyone else, in order of time (most recent to oldest): 2cbd9f1d77ce6b25e9957d3121fccb521caf848f - 3c5246b1fb2ec2f9c34ba1cb5083b2745d7bdf89 - 6537dc777512d093a489cb1db99e8db8cf50b914 - Not much tuning has been done yet for the geoNear refactor. |