[SERVER-14928] $geoIntersect Poor Performance on 2.6.4 Created: 16/Aug/14 Updated: 15/Nov/21 Resolved: 23/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | 2.6.3, 2.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ygor Lemos | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Just run the sample query. |
| Participants: |
| Description |
|
geoIntersect queries are getting very long to complete (~1300ms) against a collection with 5530 polygons / multi polygons (154.41mb) The query generally returns 2 or 3 documents. Sample Query:
Query Explain Output:
Collection Stats:
Collection Indexes:
The documents are large polygon areas like states, districts and municipalities. The database is running on a Replica Set managed by Compose.io (ex MongoHQ) with a lot of idle hardware. I have MMS monitoring enabled should more stats are needed. Locks and Queues are very very low, all other queries returns very fast, including geoNear queries on other collections. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 18/Aug/14 ] |
|
the collection is small; would it be possible to mongodump the collection, compress and attach to this ticket? |