Preallocate a map of the right size in pcommon Map.AsRaw()

[kamstrup]

Description

We are seeing pcommon/Map.AsRaw() show up in the memory profiles.

This PR ensure we pre-allocate a map[string]any of the expected size, instead of just an empty map.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: kamstrup / name: Mikkel Kamstrup Erlandsen (0dabdfb, e0578fa)

[bogdandrutu]

This PR is ok, but I am curious why do you need to call this function and in which component?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.19%. Comparing base (a567a01) to head (0dabdfb).
Report is 20 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12406      +/-   ##
==========================================
+ Coverage   91.55%   92.19%   +0.64%     
==========================================
  Files         467      465       -2     
  Lines       25652    25285     -367     
==========================================
- Hits        23485    23311     -174     
+ Misses       1768     1575     -193     
  Partials      399      399              

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

[bogdandrutu]

Please add a changelog entry

[kamstrup]

Please add a changelog entry

Done :-)

[bogdandrutu]

@kamstrup ping on

but I am curious why do you need to call this function and in which component?

[kamstrup]

@kamstrup ping on

but I am curious why do you need to call this function and in which component?

Good question :-) We have custom storage engine and we do some massaging of otel payloads to store them most efficiently. We pull the attributes out as a map and rearrange the data.

When we have huge nested maps AsRaw starts to show up in the profiles. Not a deal breaker by any means, of course, but just thought it was a nice small improvement