Fix for count being very slow on large Parse Classes' collections #5264
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For newer version of parse-server (at least 3.1.2) fetching count for a Parse Class takes a very long time if the Class has lots (1M+) of rows.
This is due to the Parse-Server's internal MongoCollection class using mongoDb's db.collection.countDocuments() method, which causes all of the collection's documents to be scanned; thus making the operation extremely slow.
This should be fixed so that countDocuments is only used for counting if a query is also provided. Otherwise the much faster db.collection.estimatedDocumentCount() should be used instead.
In the PR I've updated
MongoCollection.count(...)
so that if no query is specified, then the counting is done by theestimatedDocumentCount()
method.This problem has previously been discussed in issue #5218, and similar performance issues have been discussed here for mongoose.