MongoDB slow with index and sort
I have compound index:
{
"hidden" : 1,
"country" : 1,
"edited" : 1,
"changeset.when" : -1
}
And query:
{
"country" : "ua",
"edited" : true,
"hidden" : false,
"changeset.when" : { "$lt" : ISODate("5138-11-16T09:46:40Z") }
}
It works well and fast. Now I want to sort result by: { "changeset.when" : -1 }
and it slows down a lot. From hundred of milliseconds to 15 seconds.
And here is explain for query with sorting:
"winningPlan" : {
"stage" : "SORT",
"sortPattern" : {
"changeset.when" : -1
},
"limitAmount" : 15,
"inputStage" : {
"stage" : "SORT_KEY_GENERATOR",
"inputStage" : {
"stage" : "FETCH",
"inputStage" : {
"stage" : "IXSCAN",
"keyPattern" : {
"hidden" : 1,
"country" : 1,
"edited" : 1,
"changeset.when" : -1
},
"indexName" : "edited_news",
"isMultiKey" : true,
"multiKeyPaths" : {
"hidden" : [ ],
"country" : [ ],
"edited" : [ ],
"changeset.when" : [
"changeset"
]
},
"isUnique" : false,
"isSparse" : false,
"isPartial" : false,
"indexVersion" : 2,
"direction" : "forward",
"indexBounds" : {
"hidden" : [
"[false, false]"
],
"country" : [
"["ua", "ua"]"
],
"edited" : [
"[true, true]"
],
"changeset.when" : [
"(new Date(100000000000000), true)"
]
}
}
}
}
}
Why is it so slow? Explain shows that it successfully uses needed index and field changeset.when
is in descending order.
mongodb indexing
add a comment |
I have compound index:
{
"hidden" : 1,
"country" : 1,
"edited" : 1,
"changeset.when" : -1
}
And query:
{
"country" : "ua",
"edited" : true,
"hidden" : false,
"changeset.when" : { "$lt" : ISODate("5138-11-16T09:46:40Z") }
}
It works well and fast. Now I want to sort result by: { "changeset.when" : -1 }
and it slows down a lot. From hundred of milliseconds to 15 seconds.
And here is explain for query with sorting:
"winningPlan" : {
"stage" : "SORT",
"sortPattern" : {
"changeset.when" : -1
},
"limitAmount" : 15,
"inputStage" : {
"stage" : "SORT_KEY_GENERATOR",
"inputStage" : {
"stage" : "FETCH",
"inputStage" : {
"stage" : "IXSCAN",
"keyPattern" : {
"hidden" : 1,
"country" : 1,
"edited" : 1,
"changeset.when" : -1
},
"indexName" : "edited_news",
"isMultiKey" : true,
"multiKeyPaths" : {
"hidden" : [ ],
"country" : [ ],
"edited" : [ ],
"changeset.when" : [
"changeset"
]
},
"isUnique" : false,
"isSparse" : false,
"isPartial" : false,
"indexVersion" : 2,
"direction" : "forward",
"indexBounds" : {
"hidden" : [
"[false, false]"
],
"country" : [
"["ua", "ua"]"
],
"edited" : [
"[true, true]"
],
"changeset.when" : [
"(new Date(100000000000000), true)"
]
}
}
}
}
}
Why is it so slow? Explain shows that it successfully uses needed index and field changeset.when
is in descending order.
mongodb indexing
Try puttingchangeset.when
as the first entry in the index or creating a single key index on that field.. See docs.mongodb.com/manual/tutorial/sort-results-with-indexes
– Paul
Nov 13 '18 at 16:01
add a comment |
I have compound index:
{
"hidden" : 1,
"country" : 1,
"edited" : 1,
"changeset.when" : -1
}
And query:
{
"country" : "ua",
"edited" : true,
"hidden" : false,
"changeset.when" : { "$lt" : ISODate("5138-11-16T09:46:40Z") }
}
It works well and fast. Now I want to sort result by: { "changeset.when" : -1 }
and it slows down a lot. From hundred of milliseconds to 15 seconds.
And here is explain for query with sorting:
"winningPlan" : {
"stage" : "SORT",
"sortPattern" : {
"changeset.when" : -1
},
"limitAmount" : 15,
"inputStage" : {
"stage" : "SORT_KEY_GENERATOR",
"inputStage" : {
"stage" : "FETCH",
"inputStage" : {
"stage" : "IXSCAN",
"keyPattern" : {
"hidden" : 1,
"country" : 1,
"edited" : 1,
"changeset.when" : -1
},
"indexName" : "edited_news",
"isMultiKey" : true,
"multiKeyPaths" : {
"hidden" : [ ],
"country" : [ ],
"edited" : [ ],
"changeset.when" : [
"changeset"
]
},
"isUnique" : false,
"isSparse" : false,
"isPartial" : false,
"indexVersion" : 2,
"direction" : "forward",
"indexBounds" : {
"hidden" : [
"[false, false]"
],
"country" : [
"["ua", "ua"]"
],
"edited" : [
"[true, true]"
],
"changeset.when" : [
"(new Date(100000000000000), true)"
]
}
}
}
}
}
Why is it so slow? Explain shows that it successfully uses needed index and field changeset.when
is in descending order.
mongodb indexing
I have compound index:
{
"hidden" : 1,
"country" : 1,
"edited" : 1,
"changeset.when" : -1
}
And query:
{
"country" : "ua",
"edited" : true,
"hidden" : false,
"changeset.when" : { "$lt" : ISODate("5138-11-16T09:46:40Z") }
}
It works well and fast. Now I want to sort result by: { "changeset.when" : -1 }
and it slows down a lot. From hundred of milliseconds to 15 seconds.
And here is explain for query with sorting:
"winningPlan" : {
"stage" : "SORT",
"sortPattern" : {
"changeset.when" : -1
},
"limitAmount" : 15,
"inputStage" : {
"stage" : "SORT_KEY_GENERATOR",
"inputStage" : {
"stage" : "FETCH",
"inputStage" : {
"stage" : "IXSCAN",
"keyPattern" : {
"hidden" : 1,
"country" : 1,
"edited" : 1,
"changeset.when" : -1
},
"indexName" : "edited_news",
"isMultiKey" : true,
"multiKeyPaths" : {
"hidden" : [ ],
"country" : [ ],
"edited" : [ ],
"changeset.when" : [
"changeset"
]
},
"isUnique" : false,
"isSparse" : false,
"isPartial" : false,
"indexVersion" : 2,
"direction" : "forward",
"indexBounds" : {
"hidden" : [
"[false, false]"
],
"country" : [
"["ua", "ua"]"
],
"edited" : [
"[true, true]"
],
"changeset.when" : [
"(new Date(100000000000000), true)"
]
}
}
}
}
}
Why is it so slow? Explain shows that it successfully uses needed index and field changeset.when
is in descending order.
mongodb indexing
mongodb indexing
asked Nov 13 '18 at 15:54
OckonalOckonal
19.8k65163279
19.8k65163279
Try puttingchangeset.when
as the first entry in the index or creating a single key index on that field.. See docs.mongodb.com/manual/tutorial/sort-results-with-indexes
– Paul
Nov 13 '18 at 16:01
add a comment |
Try puttingchangeset.when
as the first entry in the index or creating a single key index on that field.. See docs.mongodb.com/manual/tutorial/sort-results-with-indexes
– Paul
Nov 13 '18 at 16:01
Try putting
changeset.when
as the first entry in the index or creating a single key index on that field.. See docs.mongodb.com/manual/tutorial/sort-results-with-indexes– Paul
Nov 13 '18 at 16:01
Try putting
changeset.when
as the first entry in the index or creating a single key index on that field.. See docs.mongodb.com/manual/tutorial/sort-results-with-indexes– Paul
Nov 13 '18 at 16:01
add a comment |
1 Answer
1
active
oldest
votes
In case if you have compound index try to create query key sequence like your index sequencency. It will bring more performance.
You don't need to make aditional sort for result, by default result will be sorted according index (in your case result will be sorted descending by changeset.when
)
For more info please share some documents from your collection.
If you have any question feel free to ask
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53284769%2fmongodb-slow-with-index-and-sort%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In case if you have compound index try to create query key sequence like your index sequencency. It will bring more performance.
You don't need to make aditional sort for result, by default result will be sorted according index (in your case result will be sorted descending by changeset.when
)
For more info please share some documents from your collection.
If you have any question feel free to ask
add a comment |
In case if you have compound index try to create query key sequence like your index sequencency. It will bring more performance.
You don't need to make aditional sort for result, by default result will be sorted according index (in your case result will be sorted descending by changeset.when
)
For more info please share some documents from your collection.
If you have any question feel free to ask
add a comment |
In case if you have compound index try to create query key sequence like your index sequencency. It will bring more performance.
You don't need to make aditional sort for result, by default result will be sorted according index (in your case result will be sorted descending by changeset.when
)
For more info please share some documents from your collection.
If you have any question feel free to ask
In case if you have compound index try to create query key sequence like your index sequencency. It will bring more performance.
You don't need to make aditional sort for result, by default result will be sorted according index (in your case result will be sorted descending by changeset.when
)
For more info please share some documents from your collection.
If you have any question feel free to ask
answered Nov 14 '18 at 8:20
andranikaslandranikasl
38924
38924
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53284769%2fmongodb-slow-with-index-and-sort%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Try putting
changeset.when
as the first entry in the index or creating a single key index on that field.. See docs.mongodb.com/manual/tutorial/sort-results-with-indexes– Paul
Nov 13 '18 at 16:01