When I read the document I found the following notes:
When a $sort immediately precedes a $limit in the pipeline, the $sort operation only maintains the top n results as it progresses, where n is the specified limit, and MongoDB only needs to store n items in memory. This optimization still applies when allowDiskUse is true and the n items exceed the aggregation memory limit.
If I'm right about this, it applies only when I use the $sort and $limit together like
db.coll.aggregate([
...,
{$sort: ...},
{$limit: limit},
...
]);
However, I think most of the time we would have
db.coll.aggregate([
...,
{$sort: ...},
{$skip: skip},
{$limit: limit},
...
]);
Question 1: Does it mean the rule above doesn't apply if I use $skip here?
I ask this question because theoretically MongoDB can still calculate the top n records and enhance performance by sorting only top n records. I didn't find any document about this though. And if the rule doesn't apply,
Question 2: Do I need to change my query to the following to enhance performance?
db.coll.aggregate([
...,
{$sort: ...},
{$limit: skip + limit},
{$skip: skip},
{$limit: limit},
...
]);
EDIT: I think explains my use case would make the question above makes more sense. I'm using the text search feature provided by MongoDB 2.6 to look for products. I'm worried if the user inputs a very common key word like "red", there will be too many results returned. Thus I'm looking for better ways to generate this result.
EDIT2: It turns out that the last code above equals to
db.coll.aggregate([
...,
{$sort: ...},
{$limit: skip + limit},
{$skip: skip},
...
]);
Thus I we can always use this form to make the top n rule apply.
See Question&Answers more detail:
os