Add a MongoDB index on case reference UUID fields #701
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
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.
Primarily to optimize the existing batchUpsert API, but functions for any query based on the aforementioned fields.
Trialing this on a batch upload of 10k cases, each with a unique
{sourceId,sourceEntryId}, it was about a 3X speedup (14s) as compared to running without the index (42s). Batch upserts without that UUID combo aren't impacted (since they don't query/filter on it, of course); but for reference, inserting 10k cases without the case reference UUID fields actually took slightly longer (16s) as compared to the indexed UUID-full batch upsert.