Decrease the number of padding bytes in the Node Struct so it fits a lower quanta #1580
Conversation
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
artemcm
approved these changes
Apr 10, 2024
|
@swift-ci test |
owenv
approved these changes
Apr 10, 2024
|
@swift-ci test Windows platform |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Heap --showInternalFragmentation shows that we are loosing 14 bytes to padding in Node instances.
Class: 'Node' [instance size 104, allocation size 112] - Swift, ARC {
...
}
16: keyAndFingerprint;
<< 7 alignment bytes >>
64: definitionLocation;
88: isTraced;
<< 7 alignment bytes >>
96: cachedHash;
}
Moving isTraced up here will push Node instance allocations to the next quanta (96)