Reduce size of ClassInfoCache by 32 bytes per cache entry#56
Merged
Conversation
…from long to int This gives us 4,294,967,295 update ticks which is still enough for a long running app given we only bump the tick count when a new class definition is shared in the cache.
PerfectSlayer
approved these changes
Mar 9, 2026
This file contains hidden or 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
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.
What Does This Do
Suggestion from Claude: trim cache info entry size by changing ticks from
longtointMotivation
This gives us 4,294,967,295 update ticks (min value to max value, incremented monotonically) which is still enough for a long running app given we only bump the tick count when a new class definition is shared in the cache.
Contributor Checklist
Jira ticket: [PROJ-IDENT]