Big performance degradation cause by profiles in OTTL

[bogdandrutu]

Component(s)

No response

What happened?

Because of how profiles have their schema and of the #39416 every map operation now forces a copy of the Map in the Setter.

I think we should consider an immediate rollback and then consider a proper fix where the Setter is no-op where it can be no-op.

Collector version

v0.133.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

Log output

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[bogdandrutu]

@rockdaboot @dmathieu

[github-actions]

Pinging code owners for pkg/ottl: @TylerHelmuth @evan-bradley @edmocosta. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[edmocosta]

I saw you've opened open-telemetry/opentelemetry-collector#13731. I think we can also make it no-op in OTTL (all signals but profiles) by doing a similar check, something like #42358 would work for now.

[edmocosta]

Considering open-telemetry/opentelemetry-collector#13731 fixed it, and that all affected functions were map-based, we probably don't need to handle it from the OTTL side anymore (other than adding benchmarks). Please feel free to re-open if you think otherwise.