-
Notifications
You must be signed in to change notification settings - Fork 829
Add OTLP Benchmark to measure push performance #6977
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
base: master
Are you sure you want to change the base?
Add OTLP Benchmark to measure push performance #6977
Conversation
Signed-off-by: SungJin1212 <[email protected]>
Currently, our I was thinking we could manage a dedicated Cortex converter, which can directly convert OTLP to Cortex format. This would allow us to skip the intermediate conversion from Prometheus format to Cortex. If the case, the memory allocation will be reduced, but this is expected to come at the cost of tracking overhead. @yeya24 @friedrichg |
Hey @SungJin1212, I think that makes sense. But at the same time, do we have a benchmark to understand OTLP performance? If not let's create one so that we can compare the performance impact and its baseline |
@yeya24 |
Signed-off-by: SungJin1212 <[email protected]>
@yeya24 |
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.
Thanks!
Signed-off-by: SungJin1212 <[email protected]>
This PR adds a benchmark to measure OTLP push performance.
The Benchmark results are:
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]