Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize the memory footprint of MapMakerInternalMap entries by special-casing linked entries. #6197

Closed
wants to merge 0 commits into from

Conversation

copybara-service[bot]
Copy link
Contributor

Optimize the memory footprint of MapMakerInternalMap entries by special-casing linked entries.

The first entry in each bucket does not need a next field because it will only ever be the tail of the bucket's linked list. Because MapMakerInternalMap uses a load factor of 0.75, we can expect that most entries are tails, so long as the hash function is good.

For the common use case of a weak interner with compressed OOPs, omitting the next field reduces the shallow heap of WeakKeyDummyValueEntry from 40 bytes to 32 bytes.

RELNOTES=Memory optimizations for Interner and MapMaker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants