fix(perf regression): TopicName parsing per publish #2304
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.
Fixes #2295
i believe this was introduced in db522b6
With the same reproducer as in the issue. From testing it seems to improve throughput by 10%
Profile before
producer_load_test_v1.zip
Profile after
producer_load_test_after_optimization_v1.zip
Note: I believe there is a similar problem in
OpenTelemetryPubsubTracer.startPublishRpcSpan
. But I kept the scope of this PR to a minimum.