What is the recommended memory limiter/ballast config following the ballast deprecation?

[bonnici]

The Memory Limiter Processor README file still says:

It is highly recommended to configure ballastextension as well as the memory_limiter processor on every collector. The ballast should be configured to be 1/3 to 1/2 of the memory allocated to the collector. The memory_limiter processor should be the first processor defined in the pipeline (immediately after the receivers). This is to ensure that backpressure can be sent to applicable receivers and minimize the likelihood of dropped data when the memory_limiter gets triggered.

The v0.92 changelog lists the ballast extension as deprecated. What is the new recommended config to use? Should we set GOMEMLIMIT to be what the old ballast size was?

[atoulme]

Feel free to review and accept or provide comments to this PR as it touches that file: #9152

[bonnici]

Thank you! That made it more clear - I've set memory limit to about 90% of the available memory, spike limit to about 20% of that, and GOMEMLIMIT to about 20% lower than the 90% hard limit. I don't think I should accept the PR though since I'm pretty clueless about Go and how it uses memory.

[atoulme]

No worries. Happy that helped.