Optimize substr_matching with the Aho-Corasick algorithm#45
Merged
howardhsu merged 1 commit intofacebookresearch:mainfrom Mar 25, 2024
Merged
Conversation
Contributor
|
that's a great idea to improve the existing brute-force matching, thx a lot for the contribution. will refactor slightly later. |
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
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.
I optimized the substr_matching algorithm by integrating the Aho-Corasick Algorithm.
Which prints in my laptop:
Please do consider that the outpout of the new substr_matching will not be ordered now. If you need it to be ordered, you can change the last line to
sorted(list(matched_entry_ids))I appreciate that you want to reduce dependencies for the repo, but considering that the use-case is building massive datasets, this sounds like a sensible improvement to me. What do you think? Is there some context I'm missing?