opentelemetry: add preliminary benchmarks #1303
Merged
Conversation
This file contains 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
## Motivation Understand the overhead added by recording OpenTelemetry data so that it can be minimized. ## Solution Add criterion benchmarks, initially tracking request/response style workloads (1 main span with 99 children). This patch adds benchmarks for standard `tracing-opentelemetry` usage, as well as baselines for understanding the overhead specific to the usage of the otel tracer, and registry span access patterns.
davidbarsky
approved these changes
Mar 15, 2021
|
I just ran the benchmark on my Mac. Seems like
|
|
@Folyd the otel overhead is mostly in sampling, constructing otel spans from tracing spans, and reporting otel spans to exporters. Each of those can be optimized, feel free to open issues on https://github.com/open-telemetry/opentelemetry-rust if you find perf problems. |
hawkw
pushed a commit
that referenced
this pull request
Apr 15, 2021
## Motivation Understand the overhead added by recording OpenTelemetry data so that it can be minimized. ## Solution Add criterion benchmarks, initially tracking request/response style workloads (1 main span with 99 children). This patch adds benchmarks for standard `tracing-opentelemetry` usage, as well as baselines for understanding the overhead specific to the usage of the otel tracer, and registry span access patterns.
hawkw
pushed a commit
that referenced
this pull request
Apr 15, 2021
## Motivation Understand the overhead added by recording OpenTelemetry data so that it can be minimized. ## Solution Add criterion benchmarks, initially tracking request/response style workloads (1 main span with 99 children). This patch adds benchmarks for standard `tracing-opentelemetry` usage, as well as baselines for understanding the overhead specific to the usage of the otel tracer, and registry span access patterns.
Merged
hawkw
pushed a commit
that referenced
this pull request
Apr 17, 2021
## Motivation Understand the overhead added by recording OpenTelemetry data so that it can be minimized. ## Solution Add criterion benchmarks, initially tracking request/response style workloads (1 main span with 99 children). This patch adds benchmarks for standard `tracing-opentelemetry` usage, as well as baselines for understanding the overhead specific to the usage of the otel tracer, and registry span access patterns.
kaffarell
pushed a commit
to kaffarell/tracing
that referenced
this pull request
May 22, 2024
## Motivation Understand the overhead added by recording OpenTelemetry data so that it can be minimized. ## Solution Add criterion benchmarks, initially tracking request/response style workloads (1 main span with 99 children). This patch adds benchmarks for standard `tracing-opentelemetry` usage, as well as baselines for understanding the overhead specific to the usage of the otel tracer, and registry span access patterns.
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.
Motivation
Understand the overhead added by recording OpenTelemetry data so that it can be minimized.
Solution
Add criterion benchmarks, initially tracking request/response style workloads (1 main span with 99 children).
This patch adds benchmarks for standard
tracing-opentelemetryusage, as well as baselines for understanding the overhead specific to the usage of the otel tracer, and registry span access patterns.