From ca28e6873ef92f819fb92122e76043db00dd3cb7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Spiegel?= Date: Mon, 22 Sep 2014 16:47:17 -0400 Subject: [PATCH] Be more precise about in-memory sorting limit I asked kernel engineering what exactly the size limit for in-memory sort was, and it turns out it's the size of all sorted documents combined. --- source/reference/limits.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/source/reference/limits.txt b/source/reference/limits.txt index 4709b4e0134..54e2f6b1cbf 100644 --- a/source/reference/limits.txt +++ b/source/reference/limits.txt @@ -316,8 +316,9 @@ Operations .. limit:: Sorted Documents MongoDB will only return sorted results on fields without an index - *if* the sort operation uses less than 32 megabytes of memory. - + *if* the combined size of all documents to be sorted (plus some overhead) + is less than 32 megabytes. + .. _limit-agg-sort: .. limit:: Aggregation Pipeline Operation