We run perf in continuous mode, and signal it every interval to dump the data it has collected so far.
If gProfiler for whatever reason does not signal perf, perf will continue accumulating data on disk and there is no limit placed on it. This can happen if gprofiler gets stuck, for example.
What I'd like to have is - perf will automatically stop collecting data after a set interval, like the timeout parameter that we have for async-profiler which stops it after a while. If the interval is X, we could have perf time out after 1.5X time. That's one option. Another option is to cycle the data in the dumped file.
First let's see if perf has any such feature we can use; if not, I suggest we add it to perf with a flag, and pass that flag from gprofiler.
We run perf in continuous mode, and signal it every interval to dump the data it has collected so far.
If gProfiler for whatever reason does not signal perf, perf will continue accumulating data on disk and there is no limit placed on it. This can happen if gprofiler gets stuck, for example.
What I'd like to have is - perf will automatically stop collecting data after a set interval, like the
timeoutparameter that we have for async-profiler which stops it after a while. If the interval is X, we could have perf time out after 1.5X time. That's one option. Another option is to cycle the data in the dumped file.First let's see if perf has any such feature we can use; if not, I suggest we add it to perf with a flag, and pass that flag from gprofiler.