feat: introduce a text compress for search function #2454
Closed
Conversation
This file contains hidden or 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
closed via #2464 . |
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.
Summary
The search INDEX we store in
localStorage, and it has the limitation about 5M.And we discussed about the
Indexed DBand other solutions couple years ago.Today, a sudden inspiration struck me: instead of switching the persistence layer, we can use text compression to address our retrieval needs.
So I have found some implementations of text compression algorithms，and pick the suitable one of LZW lz-string since we are more on the content/docs.
Have a test based on our site docs, it reduces the 80% cost.
In short term, it could be a chance for users to make search still works when their docs big but not that too much.
Related issue, if any:
What kind of change does this PR introduce?
Feature
For any code change,
Does this PR introduce a breaking change?
Yes
No
No
Tested in the following browsers: