Optimize performance of GetHashCode for ContentType comparers, remove allocs #9723
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.
Description
Removes allocations for
ContentType
'sWeakComparer
andStrongComparer
(which are used in the related dictionaries).StringComparer.OrdinalIgnoreCase.GetHashCode(src)
instead ofsrc.ToUpperInvariant.GetHashCode()
as that creates a new string everytime just so we can retrieve HashCode out of it.Benchmarks
Benchmark code
Customer Impact
Increased performance, including start-up performance, decreased allocations.
Regression
No.
Testing
Local build, assert test:
Risk
Low.
Microsoft Reviewers: Open in CodeFlow