Faster unicode string compare#2180
Draft
christopherlam wants to merge 2 commits intoGnucash:stablefrom
Draft
Conversation
Member
|
Micro benchmarks like that only show that the micro benchmark benefits from the change. They don't demonstrate anything about the program. Profile GnuCash and show where creating a collator makes a hot path.
Don't use |
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 still think that unicode collator needs to be cached; it's heavily used by ui and report code everywhere... Here's benchmark comparing 5M strings. Without caching:
With caching:
Also instead of returning
-99how about logging an ICU failure and returningg_strcmp0 (one,two)?