You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
OTTL currently has some basic performance benchmarks, but they are not comprehensive or detailed enough to show the full performance picture.
Describe the solution you'd like
We would like to have a comprehensive and rigorous set of performance benchmarks. The goal is to provide clear, measurable data that validates our decision to build OTTL as a native OTLP solution and highlight areas where performance can be improved.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
@evan-bradley. Yes, I have some open cycles this quarter, so I'd be happy to take this.
I am thinking of starting off with some common use cases (like what you and Tyler covered last week https://www.youtube.com/watch?v=UGTU0-KT_60) and see how filter processor / transform processor handles huge traffic. Let me know if you have any ideas / advices.
A benchmark for how the transformprocessor handles under load while handling many statements (like 100+ transformations) would also be great. I have seen some very large transformprocessor configs.
Component(s)
pkg/ottl
Is your feature request related to a problem? Please describe.
OTTL currently has some basic performance benchmarks, but they are not comprehensive or detailed enough to show the full performance picture.
Describe the solution you'd like
We would like to have a comprehensive and rigorous set of performance benchmarks. The goal is to provide clear, measurable data that validates our decision to build OTTL as a native OTLP solution and highlight areas where performance can be improved.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: