Optimize OTEL agent memory usage

[rahuldimri]

Component(s)

No response

Describe the issue you're reporting

Currently we see that OTEL agent (deployed on user's K8s cluster) consumes lot of memory as data increases. It would be helpful if we could optimize agent so it uses less memory.

[crobert-1]

Hello @rahuldimri, can you the full configuration that you're using that is consuming a lot of memory? Do you see memory usage growing over time? Can you expand on what you mean as data increases? Is this relevant for a specific version of the collector (has one version been better or worse than another)? Can you share any specifics on how much memory is being consumed?

This will all be helpful in trying to determine the root cause of the issue you're seeing.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.