-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the collector exporter mutate data, and remove unnecessary CopyTo #892
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #892 +/- ##
==========================================
+ Coverage 61.03% 63.03% +1.99%
==========================================
Files 56 57 +1
Lines 5903 5967 +64
==========================================
+ Hits 3603 3761 +158
+ Misses 2143 2044 -99
- Partials 157 162 +5 ☔ View full report in Codecov by Sentry. |
|
It's weird the benchmarks now have |
I only did |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where is the actual flag indicating that the exporter is mutating? I'm guessing collector-contrib in a separate PR
exporter/collector/internal/normalization/disabled_normalizer.go
Outdated
Show resolved
Hide resolved
It is an option to exporterhelper: https://pkg.go.dev/go.opentelemetry.io/collector/exporter/exporterhelper#WithCapabilities, which we will need to set in our exporters |
Looking at #890 (comment)
This change makes the collector exporter now mutate data. We were doing multiple layers additional copying in our exporter to prevent mutating data, but it is likely better for us to just be a mutating exporter, and let the framework handle it.
This keeps the collector code clean, and should have better CPU/Memory usage (even after the additional copy) since we are copying fewer times.
Benchmarks (including those added in #893):