Yeah, it scales badly with the number of markers you have to process, and it’s done on the MainThread only, so to speed up processing do short recordings, or use selective deep profiling.
Overall, with deep profiling, the timings you capture will be quite off as the cost of having each function call instrumented with the number of calls becomes high so you could make wrong assumptions on the performance of your code. Instead, I’d recommend employing profiler markers to instrument the code of interest (specific method, a chain of methods, etc) and using a regular unity profiler with extra markers you’ve added by hand. Another thing you may consider is trying Selective Deep profiling. Alternatively, other types of profilers (sampling profilers) allow capturing the full callstack at specific frequencies (Android Studio, Intel VTune, Superluminal, Xcode Instruments, etc).