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: bogdandrutu / name: Bogdan Drutu (305c92d)
• ✅ 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.10%. Comparing base (cffb7b6) to head (305c92d).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #12406   +/-   ##
=======================================
  Coverage   92.10%   92.10%           
=======================================
  Files         465      465           
  Lines       25180    25180           
=======================================
  Hits        23191    23191           
  Misses       1592     1592           
  Partials      397      397           

☔ 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