MongoDB Indexing - How many fields should I index?
I have a Collection in my db, called Post.
Here's how it looks:
Post {
user: <EmbeddedObject>,
school: <EmbeddedObject>,
hashtag: <EmbeddedObject>,
numberOfReports: <Number>,
viewRanking: <Number>,
type: <String>,
isPollOfTheDay: <Bool>,
createdAt: <Date>,
endsAt: <Date>
}
(Obviously it also contains other, unrelated fields)
So this Post collection, is being queried by 5 different screens in my app. School, Hashtag, All Polls, Discover & Profile. All queries are very similar to each other, but they differ.
Let's have a look at them individually:
School
Here, I have 2 queries
I compare by
school.name(equal to),numberOfReports(less than),user.id(for blocks checking (not contained in)) and lastly, we sort in descending order either bycreatedAtorviewRanking(depends on the user)I compare by
isPollOfTheDay(equal totrue) andendsAt(greater than or equal to)
Hashtag
I compare by hashtag.id (equal to), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order either by createdAt or viewRanking (depends on the user)
All Polls
I compare by type (equal to), isPollOfTheDay (equal to false), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order either by createdAt or viewRanking (depends on the user)
Discover
I compare by school.name (not equal to), type (equal to), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order by createdAt
Profile
I compare by user.id (equal to) and we sort in descending order by createdAt
These are all of my queries! I can say that they are called almost with the same frequency. My question is, should I just index all 9 fields? Are they too many to index? Should I ignore the isPollOfTheDay field, since it's a Boolean? (I've read that we shouldn't index Booleans)
index mongodb
asked 1 hour ago
Sotiris KanirasSotiris Kaniras
1184
add a comment |
I have a Collection in my db, called Post.
Here's how it looks:
Post {
user: <EmbeddedObject>,
school: <EmbeddedObject>,
hashtag: <EmbeddedObject>,
numberOfReports: <Number>,
viewRanking: <Number>,
type: <String>,
isPollOfTheDay: <Bool>,
createdAt: <Date>,
endsAt: <Date>
}
(Obviously it also contains other, unrelated fields)
So this Post collection, is being queried by 5 different screens in my app. School, Hashtag, All Polls, Discover & Profile. All queries are very similar to each other, but they differ.
Let's have a look at them individually:
School
Here, I have 2 queries
I compare by
school.name(equal to),numberOfReports(less than),user.id(for blocks checking (not contained in)) and lastly, we sort in descending order either bycreatedAtorviewRanking(depends on the user)I compare by
isPollOfTheDay(equal totrue) andendsAt(greater than or equal to)
Hashtag
I compare by hashtag.id (equal to), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order either by createdAt or viewRanking (depends on the user)
All Polls
I compare by type (equal to), isPollOfTheDay (equal to false), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order either by createdAt or viewRanking (depends on the user)
Discover
I compare by school.name (not equal to), type (equal to), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order by createdAt
Profile
I compare by user.id (equal to) and we sort in descending order by createdAt
These are all of my queries! I can say that they are called almost with the same frequency. My question is, should I just index all 9 fields? Are they too many to index? Should I ignore the isPollOfTheDay field, since it's a Boolean? (I've read that we shouldn't index Booleans)
index mongodb
asked 1 hour ago
Sotiris KanirasSotiris Kaniras
1184
add a comment |
I have a Collection in my db, called Post.
Here's how it looks:
Post {
user: <EmbeddedObject>,
school: <EmbeddedObject>,
hashtag: <EmbeddedObject>,
numberOfReports: <Number>,
viewRanking: <Number>,
type: <String>,
isPollOfTheDay: <Bool>,
createdAt: <Date>,
endsAt: <Date>
}
(Obviously it also contains other, unrelated fields)
So this Post collection, is being queried by 5 different screens in my app. School, Hashtag, All Polls, Discover & Profile. All queries are very similar to each other, but they differ.
Let's have a look at them individually:
School
Here, I have 2 queries
I compare by
school.name(equal to),numberOfReports(less than),user.id(for blocks checking (not contained in)) and lastly, we sort in descending order either bycreatedAtorviewRanking(depends on the user)I compare by
isPollOfTheDay(equal totrue) andendsAt(greater than or equal to)
Hashtag
I compare by hashtag.id (equal to), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order either by createdAt or viewRanking (depends on the user)
All Polls
I compare by type (equal to), isPollOfTheDay (equal to false), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order either by createdAt or viewRanking (depends on the user)
Discover
I compare by school.name (not equal to), type (equal to), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order by createdAt
Profile
I compare by user.id (equal to) and we sort in descending order by createdAt
These are all of my queries! I can say that they are called almost with the same frequency. My question is, should I just index all 9 fields? Are they too many to index? Should I ignore the isPollOfTheDay field, since it's a Boolean? (I've read that we shouldn't index Booleans)
index mongodb
asked 1 hour ago
Sotiris KanirasSotiris Kaniras
1184
I have a Collection in my db, called Post.
Here's how it looks:
Post {
user: <EmbeddedObject>,
school: <EmbeddedObject>,
hashtag: <EmbeddedObject>,
numberOfReports: <Number>,
viewRanking: <Number>,
type: <String>,
isPollOfTheDay: <Bool>,
createdAt: <Date>,
endsAt: <Date>
}
(Obviously it also contains other, unrelated fields)
So this Post collection, is being queried by 5 different screens in my app. School, Hashtag, All Polls, Discover & Profile. All queries are very similar to each other, but they differ.
Let's have a look at them individually:
School
Here, I have 2 queries
I compare by
school.name(equal to),numberOfReports(less than),user.id(for blocks checking (not contained in)) and lastly, we sort in descending order either bycreatedAtorviewRanking(depends on the user)I compare by
isPollOfTheDay(equal totrue) andendsAt(greater than or equal to)
Hashtag
I compare by hashtag.id (equal to), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order either by createdAt or viewRanking (depends on the user)
All Polls
I compare by type (equal to), isPollOfTheDay (equal to false), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order either by createdAt or viewRanking (depends on the user)
Discover
I compare by school.name (not equal to), type (equal to), numberOfReports (less than), user.id (for blocks checking (not contained in)) and lastly, we sort in descending order by createdAt
Profile
I compare by user.id (equal to) and we sort in descending order by createdAt
These are all of my queries! I can say that they are called almost with the same frequency. My question is, should I just index all 9 fields? Are they too many to index? Should I ignore the isPollOfTheDay field, since it's a Boolean? (I've read that we shouldn't index Booleans)
index mongodb
index mongodb
asked 1 hour ago
Sotiris KanirasSotiris Kaniras
1184
asked 1 hour ago
Sotiris KanirasSotiris Kaniras
1184
asked 1 hour ago
Sotiris KanirasSotiris Kaniras
1184
asked 1 hour ago
Sotiris KanirasSotiris Kaniras
1184
asked 1 hour ago
Sotiris KanirasSotiris Kaniras
1184
1184
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2fdba.stackexchange.com%2fquestions%2f226720%2fmongodb-indexing-how-many-fields-should-i-index%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Database Administrators Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fdba.stackexchange.com%2fquestions%2f226720%2fmongodb-indexing-how-many-fields-should-i-index%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
