benchmark: add benchmark processing large OTLP messages #13677
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.
What this PR does
This add a benchmark that tests the processing of a large OTLP message marshaled to protobuf.
Which issue(s) this PR fixes or relates to
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]. If changelog entry is not needed, please add thechangelog-not-neededlabel to the PR.about-versioning.mdupdated with experimental features.Note
Adds a benchmark that measures OTLP handler performance with a large protobuf metrics payload.
BenchmarkOTLPHandlerWithLargeMessageinpkg/distributor/otel_test.goto measure processing of a large OTLP protobuf metrics request (manyResourceMetrics/Metrics/datapoints), usingOTLPHandlerwith increasedmaxMsgSize.Written by Cursor Bugbot for commit 0943231. This will update automatically on new commits. Configure here.