The Profiler only profiles code timings that are explicitly wrapped in Profiler markers. This includes the first call stack depth of invocations from Unity's native code into your scripting code, such as , , or similar methods.

The only samples you can visualize as child samples of your scripting code are those that call back into Unity’s API, if that API is instrumented, or any of your own code which has explicit Profiler marker instrumentation. Most API calls that carry a performance overhead are instrumented. For example, accessing the main Camera through the API registers as a sample.

If you want to get data about all function calls to find out where your code impacts on your application’s performance, you can use the Deep Profile setting. When you enable the Deep Profile setting, the Profiler injects profiler instrumentation into all your script methods to record all function calls, including at least the first call stack depth into any Unity API.

Deep Profiling is resource-intensive and uses a lot of memory. As a result, your application runs significantly slower while it's profiling. Deep Profiling works best for small games with simple scripting. If you use complex script code, your application might not be able to use Deep Profiling, and for many larger applications, Deep Profiling might make Unity run out of memory.

You can enable Deep Profiling if you're collecting performance data from a connected application, or if you're collecting data in the Unity Editor.

To enable Deep Profiling for a built application:

To enable Deep Profiling when you collect data in the Editor:

The Profiler then instruments all function calls when you start a profiling session.