Unity profiler delivering irrelevant information in Android case?

Question

Unity

Has anyone had issues with Unity Profiler delivering information that is too irrelevant?
On two Samsungs, I tested it through the cord (ADB) - firstly, performance immediately drops when the profiler is connected, but that's okay. But he would at least show the costs specifically for the profiler, otherwise he will throw it where he will: it will start to throw off all milliseconds in one task, then in another. Moreover, when I test without a Development Build checkbox, then the FPS is in order and it is clear that the overhead was in the wrong tasks, otherwise the application would have been sinking now.
Instead of profiling, the fight against windmills is somehow obtained. Has anyone experienced something similar?
PS
I don't remember such cases in Standalone builds. Although, maybe it's just that PC builds weren't profiled that often.

Answer 1

Everything sags approximately evenly, so if your method takes 70% of the frame time, then the problem is in it. I also advise you to place your own marks for the profiler in order to highlight narrower and more interesting zones.