[DAT-63] feat: Improve search performances #8
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
Since #6, we noticed a severe performance degradation when performing search. We measured the following: - Flexsearch search: <ms - Query cozy-client store to get file paths: ~120ms for 60 files. - Results normalization: ~3ms We used to make multiple `getById` queries to get file path, each of them taking few ms. So we tried to use a `getByIds` instead, and got ~70ms per query, which is better, but still slow. Then, we tried the following: ``` const allFiles = client.getCollectionFromState(FILES_DOCTYPE) as IOCozyFile[] const dirs = allFiles.filter(file => file.type === TYPE_DIRECTORY) return dirs.filter(dir => dirIds.includes(dir._id)) ``` This takes 2ms. We should eventually investigate why the store queries are so slow, but for now let's use this trick.
Ldoppea
approved these changes
Oct 30, 2024
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.
Since #6, we noticed a severe performance degradation when performing search.
We measured the following:
We used to make multiple
getByIdqueries to get file path, each of them taking few ms. So we tried to use agetByIdsinstead, and got ~70ms per query, which is better, but still slow.Then, we tried the following:
This takes 2ms.
We should eventually investigate why the store queries are so slow, but for now let's use this trick.