Save 8 bytes per runner.Result allocation #588
Merged
Conversation
This file contains 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
|
FYI @ehsandeep - Please, let me know your thoughts on this! This is just the struct layout change + |
Mzack9999
approved these changes
Apr 19, 2022
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.
TL;DR:
runner.Resultwasn't aligned in an optimal way leading to 8 bytes being wasted per object. Since it stores results, I believe this is an easy win that makeshttpxa little bit less resource-intensive when working on large jobs.Below you'll find the struct layout before and after. Padding (wasted, unused bytes) is seen in red color.
Old struct
Optimized struct
fieldalignmentis an official Go tool.