Refactor trailer Field for Improved Memory Efficiency and Performance #1928
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.
The original
trailer
field was represented by[]argsKV
, whereargsKV
consisted of two[]byte
slices and onebool
, totaling 56 bytes. However, maintaining each element required only a single 24-byte slice.After refactoring, there was a significant reduction in memory usage.
I designed two benchmarks to compare the performance between the refactored code and the original implementation.
BenchmarkSetTrailerBytes
primarily measures the performance of theAddTrailerBytes
function.BenchmarkSetTrailerBytesWithReset
evaluates the efficiency of reusing memory by repeatedly adding trailers and resetting.The refactoring of the
trailer
field from[]argsKV
to a single slice significantly reduced memory usage up to 51.69% and improved execution time up to 21.72%.