String Comparers benchmarks #535
Merged
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
tarekgh
approved these changes
Jun 2, 2019
jorive
reviewed
Jun 2, 2019
| public class Perf_StringComparer | ||
| { | ||
| [Params( | ||
| 128, // stackalloc path |
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.
In https://github.com/dotnet/corefx/issues/37691 it turned out that we had a huge difference for Windows vs Linux for
StringComparer.InvariantCultureIgnoreCase.I added the
GetHashCodebenchmark for https://github.com/dotnet/corefx/issues/37691 andComparebenchmarks for https://github.com/dotnet/corefx/issues/29462/cc @danmosemsft @mjsabby