Observing performance issue for opentelemetry 1.17.0

[pallavibhingarkar]

We have instrumented component with Opentelemetry 1.17.0 APIs for metrics with OTLP exporter & observing performance issue.

We need to check how we can benchmark these numbers?
Is there any way we can improve performance like java has RESUABLE_DATA option?

[pallavibhingarkar]

Please let me know what information u will need for this

[lalitb]

Can you be more specific what kind of performance issues you are observing. Is it only with upgrade to 1.17.0?

[marcalff]

Thanks for the report.

Please clarify:

• How metrics are instrumented: sync or async metrics
• What kind of metrics are used: counters, histograms, ...
• whether no / a few / a lot of attributes are added to measurements
• How many metrics are exported, and how often
• If the performance issue is a regression compared to previous releases, or if the application just started to use 1.17
• What is the observed degradation, with numbers, and compared to what baseline ?

[pallavibhingarkar]

Here are required info:

How metrics are instrumented: sync
What kind of metrics are used: counters, histograms, updowncounter, gauge
whether no / a few / a lot of attributes are added to measurements - few only tags
How many metrics are exported, and how often - 70+
If the performance issue is a regression compared to previous releases, or if the application just started to use 1.17 - just started with 1.17
What is the observed degradation, with numbers, and compared to what baseline ? - we are observing init taking time also APIs

Is there any way for improvement as we are integrating with heavy CPP application & minute performance degrade will also impact?

We observed very good result for java with RESUABLE_DATA memory mode. Not found anything like that in C++.

I see there are some performance optimization for single collector in 1.19.
Please let me know your recommendation.

[owent]

Using async instruments for exporting metrics is recommended, as sync APIs calculate hash codes for all attributes and merge data in view storages, which can be resource-intensive.

[pallavibhingarkar]

ok. Where does sync/async setting is while using opentelemetry?

[owent]

Just using Create*Observable*() APIs.