@apangin
Using a % could lead to a very large ignore window for long profiling sessions
For example if the profiling session is 1 hour => 60Minutes, we will ignore the last 6 minutes of allocations for memory leakage

At the same time using a static value like last minute could also lead to bad outcomes for short profiling sessions

I think we should have both a base static ignore window & % ignore window

We can define a base max ignore window of for example 10 seconds
And evaluate against the min value between the 10% & our base window

So for short profiling sessions we would use the % evaluation while for longer profiling sessions we would use the base max ignore window we define.

if the profiling session is 1 hour => 60Minutes, we will ignore the last 6 minutes of allocations

On the other hand, profiler will collect useful allocation data for 54 minutes - that's a lot!
If there is a continuous leak, then finding a meaningful signal in 54 minutes is just as efficient as in 59 minutes, but in the latter case, the noise will be likely higher due to young allocations that have not been freed. The problem with a constant size tail is that there always be such allocations, no matter how long profiler runs, whereas with the fixed ratio, results accuracy increases with the duration of profiling session.

The approach proposed in this PR is simple and efficient. There is no point in complicating it without obvious benefits.

@apangin As a user, I'd want to have this behavior documented, and to have the tail size configurable

@fandreuz I agree on the documentation point - will add a sentence.
As to making it configurable, I'm not sure. In my paradigm, software should just work well by default; the less things require manual configuration, the better. That said, we may add a knob in the future, if there is a demand for it.

There is a use case to record all allocations, in case the process is short-running or if this is executed as part of a CI, to verify lack of leaks. We could make the tail feature optiona, opt-out perhaps.

OK, made this configurable with --tail option. Updated docs.

Looks good to me