Use Dictionary instead of Hashtable in EventMap #4731
Merged
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
It's currently using a Hashtable with Int32 keys, which means every operation on the Hashtable boxes the int. Switching to a Dictionary removes those costs. It also lets use use TryGetValue to perform a single lookup to get a value rather than first calling ContainsKey and then using the indexer, and avoiding multiple virtual calls (most APIs on Hashtable are virtual) when we're only using the base class.
Customer Impact
Less unnecessary boxing means less pauses due to GC.
Regression
No
Testing
Just CI
Risk
Minimal. In general we prefer Dictionary over Hashtable, and the only places we're generally keeping Hashtable is when we benefit from its thread-safety guarantees, but all accesses here are protected by a lock.
You can see some of the associated costs with a microbenchmark like this: