[SERVER-22379] Performance improvement for 2d geoNear query executions Created: 29/Jan/16 Updated: 27/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Chung-yen Chang | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | qi-geo | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Integration
|
| Participants: |
| Description |
|
At one point during the 3.2 development cycle, we saw 2d geoNear queries micro-benchmarks performed at a higher throughput level (~10% better). This ticket is filed so that we can see if there are ways we can get back to the peak level that we have seen for these operations. As a target we can use git:7f1b07c and the geo.near.2d.find100 workload in mongo-perf suite for cross comparison and analysis purpose. |