Optimize string concatenation#22
Open
JohnAkindipe wants to merge 1 commit into
Open
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
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.
perf: replace string concatenation with
strings.BuilderinmakeStatsdFormatOverview
makeStatsdFormatinconsensus/pkg/api/metrics.gopreviously built its returnvalue by repeatedly concatenating onto a
stringvariable inside a loop:This has been replaced with a
strings.Builder-based implementation:Why string concatenation is inefficient
Strings in Go are immutable. Every
+=on a string does not append in-place,instead it allocates memory for a new string, copies the old string over into the new
memory location and then appends the content. This happens for every append
operation. Essentially, it leads to more memory usage and puts pressure on the
garbage collector to clean up unused memory.
Why
strings.Builderis betterstrings.Buildermaintains an internal byte buffer and is useful to efficientlybuild a string and minimize memory copying.
Benchmark results
Benchmarks were run with
-benchmem -count=3on an Intel Core i3-1005G1 @ 1.20 GHz(Go 1.26.2, linux/amd64).
Summary
Files changed
consensus/pkg/api/metrics.gomakeStatsdFormatwithstrings.Builder