Add benchmarks for the prometheus bridge #5364
Merged
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.
I wanted to get some rough numbers for how much overhead the prometheus bridge + OTLP exporter adds to pure Prometheus instrumentation, and also compare that with the Prometheus receiver vs OTLP receiver in the collector.
They aren't the best benchmarks (I used things like
top
anddocker stats
to measure), but the results broadly show what I expected, which is that is is much less expensive to do the translation client-side with the bridge, than server-side with the Prometheus Receiver.My sample code: prometheus/client_golang@main...dashpole:client_golang:benchmarking
cc @gouthamve @logicalhan