Question: How does using $expr affect performance in MongoDB?


MongoDB's $expr operator allows the use of aggregation expressions within query operations. It enables more complex queries by comparing fields from the same document or using logical conditions and mathematical computations. While $expr offers powerful capabilities, it's important to understand its impact on performance.

Performance Considerations

  1. Indexes: One of the main concerns with $expr is that it cannot take advantage of indexes in the same way as simple queries do. Since $expr expressions are more complex and compute values dynamically, MongoDB has to scan each document in the collection to evaluate the expression. This can lead to slower performance, especially in large collections.

  2. Use Case Specific: The performance impact depends heavily on how you're using $expr. For lightweight operations in smaller collections, the performance hit might be negligible. However, in large datasets, or when performing many complex calculations, the impact can be significant.

  3. Alternatives: Whenever possible, try to restructure your queries to avoid $expr if performance is a critical concern. Using straightforward queries that can leverage indexes will generally be faster. If you must use $expr, consider whether some preprocessing or denormalization of your data could simplify the queries.

  4. Aggregation Pipeline: In scenarios where $expr seems necessary, sometimes restructuring your operation into an aggregation pipeline can offer better performance. The aggregation framework is designed to handle complex operations and can often do so more efficiently than using $expr in a find query.


Consider a collection orders with documents that include fields for price and discountedPrice. If you want to find orders where the discountedPrice is less than half the price, using $expr would look like this:

db.orders.find({ $expr: { $lt: [ "$discountedPrice", { $divide: ["$price", 2] } ] } })

This query uses $expr to compare fields from the same document but won't utilize indexes on price or discountedPrice, potentially leading to a full collection scan.


While $expr provides flexibility and power for complex queries in MongoDB, it's essential to be mindful of its potential performance implications. Evaluating the specific requirements of your project and exploring alternatives can help mitigate these concerns.

Was this content helpful?

Start building today

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