opentelemetry-collector-contrib
opentelemetry-collector-contrib copied to clipboard
open-telemetry
[processor/transform] Tracing taking more CPU resources than expected
Component(s)
processor/transform
What happened?
Description
Not sure if "bug" is the right label for this, but the tracing component for the transform processor seems to be taking a significant amount of process time in high throughput scenarios.
We had a report of high CPU usage on a collector (monitoring ~10k files), and we got a profile for it. One interesting insight to come out of the profile is that ~40% of the path for the transform processor was taken by tracer::Start.
That seems like a lot of resource spent there, and this is a scenario where the collector is not configured to emit traces at all, so this effectively does nothing. I'm wondering if this is something we can optimize? I haven't looked deep enough into it just yet to understand the pitfalls.
Collector version
0.104.0
Environment information
No response
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
