Perform memory profiling and comparison benchmarking for pull requests (FF-1563) #32
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.
context
our customers expect the golang sdk to be performant and have minimal impact on their running server.
as we are making changes to the golang sdk, we need evaluate those changes for correctness. with this benchmark we will have added information to see about additional memory allocations happening with the proposed branch.
mechanism of action
make profile-memory
to producememprofile.main.out
(binary) andmemprofile.main.text
(human readible)memprofile.feat.out
andmemprofile.feat.text
filesmake profile-memory-compare BASE_FILE=memprofile1.out FEAT_FILE=memprofile2.out
In the file above we can see that several of the
json.Unmarshal
calls are removed.