The PR causes profile store to release profile objects when a new row group is flushed on disk. Currently, objects remain in memory and are not eligible for garbage collection.

Memory consumption of the ingester service has a rather interesting pattern:

Heap In-use (as reported by pprof):

In-use objects:

Where a half of the capacity is taken by convertSamples

Notice that once a new head is created, memory consumption goes to zero and then grows to ~50% of the max within the next 15-20 minutes. Supposedly, the trend indicates how samples are accumulated. However, I find it interesting that there's another "half": main contributors here are the stacktraces in-memory slice and in-memory parquet readers (that is not supposed to occupy so much memory as it only reads locations, strings, mappings, functions). Nevertheless, this is a different issue we may want to look into