feat(FormSchema): New indexes for form dashboard #77
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Loading data on the form dashboard requires a collection scan * The logic requires that a form be loaded if the user is either an admin or collaborator * Therefore, two indexes are required to fulfil this query.
arshadali172
approved these changes
Aug 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Slow queries in production for the dashboard page were the result of collection scans from a lack of relevant indexes on the form schema. The query logic requires that a form be loaded if the user is either an admin or collaborator.
Solution
Create two indexes for each query - admin or collaborator as advised by the Mongo Performance Advisor.