Improve tracing performance

[kraleppa]

We received some time this issue #956 and we kind of solved it by adding memory limit for risky processes here #972

The goal here is to research possible improvements for tracing that would decrease memory usage on heavy LiveViews

@GuzekAlan already did some research - please write in the comments your findings

[GuzekAlan]

After searching usage of :dbg.tracer I've found that there is an option to trace to file and then create trace_client which will handle it. Trace client can have a specified maximum amount of space taken via trace_port function and WrapFileSpec as parameters. The downside is that it will flush the traces in files (when accessed via trace_client). There is an option to ongoing file reads but it seems worse. Good use case for this scenerio would be stashing traces after the max_heap_size is reached, and accessing only last ones (when you enter the debugger) or reading it with intervals. I haven't made it work with debugger (storing traces worked fine but reading them didn't).

From what I've grepped this erlang tool fprof uses the file tracing (the file I've found was this one: https://github.com/KronicDeth/intellij-elixir/blob/bf061e593765f00b794b0e8e5c4fd54f0700d989/testData/org/elixir_lang/beam/decompiler/fprof.ex - should be the same but it's in elixir 🦈).