[user_events logs] Remove Arc reference from eventheader provider

[lalitb]

Changes

The Arc is not required for eventheader-provider, so removing it. This has significant perf improvements as updated in the results.

Before (refer: #142)
is_enabled:true:
1 thread: 30,866,752 iterations/sec
16 threads: 16,915,860 iterations/sec

After:
is_enabled:false
1 thread: 41,555,620 iterations/sec
16 threads: 20,119,895 iterations/sec

Merge requirement checklist

• CONTRIBUTING guidelines followed
• Unit tests added/updated (if applicable)
• Appropriate CHANGELOG.md files updated for non-trivial, user-facing changes
• Changes in public API reviewed (if applicable)

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 54.1%. Comparing base (67b30de) to head (2e9fa5c).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...pentelemetry-user-events-logs/src/logs/exporter.rs	0.0%	1 Missing ⚠️

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #143   +/-   ##
=====================================
  Coverage   54.1%   54.1%           
=====================================
  Files         42      42           
  Lines       6276    6276           
=====================================
  Hits        3401    3401           
  Misses      2875    2875           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cijothomas]

Changes

The Arc is not required for eventheader-provider, so removing it. This has nit improvement in perf too.

Before (refer: #142) is_enabled:true: 1 thread: 30,866,752 iterations/sec 16 threads: 16,915,860 iterations/sec

After: is_enabled:false 1 thread: 41,555,620 iterations/sec 16 threads: 20,119,895 iterations/sec

Merge requirement checklist

• CONTRIBUTING guidelines followed
• Unit tests added/updated (if applicable)
• Appropriate CHANGELOG.md files updated for non-trivial, user-facing changes
• Changes in public API reviewed (if applicable)

Not sure if the perf number makes sense as it appears significant. could you double check and update the description?

[lalitb]

Not sure if the perf number makes sense as it appears significant. could you double check and update the description?

Yes perf improvement is significant for single threaded scenario, and good for others too. Have updated the title, and description and also updated the results in code.