Ruby C extension speedup: don't re-intern constant string needlessly. #405
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.
Previously, the C extension interned the string "descriptor" (to obtain a Ruby
ID
value, which is an integer representation of an interned string) every time it needed to look up a descriptor object given a message class. This caused the interned-string table lookup, which uses a hashtable, to become a performance hotspot. Since the string is a constant, it makes much more sense to intern it once at initialization then use that value.Also fixed lines with > 80 char length.