Introducing Dragonfly Cloud! Learn More

Question: How does the performance of MongoDBs count differ from find?


In MongoDB, both count and find operations are commonly used to retrieve information about the documents stored in a collection. However, their performance can vary significantly based on the specifics of the query and the underlying data structure.


The count operation in MongoDB is typically used to get the number of documents that match a certain condition. There are two main methods:

  1. countDocuments(filter): Counts the number of documents matching the filter.
  2. estimatedDocumentCount(): Provides an approximation of the count of documents in a collection.

countDocuments performs an actual query against the database, applying any specified filters. It's accurate but can be slower for large collections because it scans each document to apply the filter.

db.collection.countDocuments({ status: 'active' })

estimatedDocumentCount is much faster as it uses metadata from the collection to estimate the count, without scanning documents. However, it doesn't consider the filter and might not be accurate if documents are frequently added or removed.



The find operation retrieves documents from a collection that match a query condition. Optionally, it can also project specific fields of the documents. The performance of find can vary greatly depending on the use of indexes, the complexity of the query, and the size of the dataset.

A basic find operation without any projection or complex filtering is relatively fast, especially on indexed fields. However, if you only need the count of documents, using find followed by a JavaScript length operation on the result set is inefficient compared to using countDocuments.

db.collection.find({ status: 'active' }).toArray().length // Inefficient for large datasets

Performance Considerations

  • Index Usage: Both count and find perform better when using indexed fields for filtering.
  • Operation Overhead: For counting documents, countDocuments is more efficient than performing a find followed by getting the length of the result set, especially for large data sets.
  • Data Size: Large collections can significantly affect the performance of both operations, but estimatedDocumentCount offers a quick approximation if exact numbers aren't critical.

In summary, choosing between count and find depends on your specific needs. Use countDocuments for accurate counts with filters, estimatedDocumentCount for fast approximations, and find when you need the actual documents or a subset of their fields.

Was this content helpful?

White Paper

Free System Design on AWS E-Book

Download this early release of O'Reilly's latest cloud infrastructure e-book: System Design on AWS.

Free System Design on AWS E-Book

Start building today 

Dragonfly is fully compatible with the Redis ecosystem and requires no code changes to implement.