[testing] Lower default r2r NativeHashtable fill factor to improve runtime lookup performance #110411
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 some startup measurements we spend a lot of time looking up r2r entry points. One potential remedy for this is to lower the fill factor for the hashtable used to perform these lookups, so that each bucket contains fewer methods and we have fewer methods to check as a result. This will raise the size of r2r images by Some Amount, and it's possible that changing it could break something, so I'm opening this draft PR to do an outerloop run and see if anything falls over.