-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Api optimization #33
Merged
Merged
Api optimization #33
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
seankim658
added
documentation
Improvements or additions to documentation
enhancement
New feature or request
labels
Jun 12, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Switched from the indirect method using an intermediary results collection to passing the burden of computation to the database by using the MongoDB aggregation framework. This helped significantly with large disk retrievals.
Before a text search with a generic term such as "cancer" required significant batching and cold start disk retrievals could take 5-7+ seconds for retrieving from disk. Implemented a naive LRU caching solution that took repeat batch retrievals from averaging ~2 seconds to ~0.02 seconds. However, this still did not fix the root cause of a cache cold start on the initial text queries. Putting the burden of processing onto the database and removing the two step list ID process got large retrievals on cold starts down significantly, from averaging ~35 seconds before to ~5 seconds.
Further optimizing, the wildcard text index was not ideal as the data model has a significant amount of nesting and fields. By manually creating an internal field that concatenated the string values from each string field into one field called
all_text
, this allowed for text indexing theall_text
field directly and dropping the wildcard text index. This dropped vague queries down to ~2.5 seconds.