-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: 3.0.2
-
Component/s: Geo
-
Query Integration
I have a collection with 300,000 documents. In collection there is a 2dsphere index on 'geo' field.
Here is a query I run:
db.runCommand(
);
Stats of this query are weird:
stats:
In the query I limit results to 500 documents. But in stats I see that mongoDB reads 80166 (objectsLoaded) documents from disk and only then cuts it out.
No need to read extra documents from disk if there is a limit on result length.
- is related to
-
SERVER-26974 Poor 2dsphere / $near performance and inconsistent object scanning
- Closed
- related to
-
SERVER-29228 geoNear scans too many records in very density area
- Backlog