-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[pkg/ottl] Add additional performance benchmarks #36463
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@sfc-gh-sili It would be great to have a better picture of OTTL's performance. Is this something you're willing to take on? |
@evan-bradley. Yes, I have some open cycles this quarter, so I'd be happy to take this. |
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. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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: