[3.x] Cache results for TranslationServer.compare_locales()
#98234
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
timothyqiu
added
enhancement
topic:core
cherrypick:3.6
|
This looks great! Do we know which PR caused this regression in performance out of interest? |
|
|
lawnjelly
approved these changes
Oct 16, 2024
bruvzg
approved these changes
Oct 17, 2024
|
Thanks! |
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.
Resolves #98228
The score for the match between two locales does not change with external circumstances. We can cache the result to avoid doing heavy string operations like
split()repeatedly.FPS is about seven times what it was before the change using the MRP here: