Since you don't need the count, you should make sure the query will return after it found the first match. Since count performance is not ideal, that is rather important. The following query should accomplish that:
db.Collection.find({ /* criteria */}).limit(1).size();
Note that find().count()
by default does not honor the limit
clause and might hence return unexpected results (and will try to find all matches). size()
or count(true)
will honor the limit flag.
If you want to go to extremes, you should make sure that your query uses covered indexes. Covered indexes only access the index, but they require that the field you query on is indexed. In general, that should do it because a count()
obviously does not return any fields. Still, covered indexes sometimes need rather verbose cursors:
db.values.find({"value" : 3553}, {"_id": 0, "value" : 1}).limit(1).explain();
{
// ...
"cursor" : "BtreeCursor value_1",
"indexOnly" : true, // covered!
}
Unfortunately, count()
does not offer explain()
, so whether it's worth it or not is hard to say. As usual, measurement is a better companion than theory, but theory can at least save you from the bigger problems.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…