The ProfilerA window that helps you to optimize your game. It shows how much time is spent in the various areas of your game. For example, it can report the percentage of time spent rendering, animating, or in your game logic. More info
See in Glossary only profiles code timings that are explicitly wrapped in Profiler markersPlaced in code to describe a CPU or GPU event that is then displayed in the Unity Profiler window. Added to Unity code by default, or you can use ProfilerMarker API to add your own custom markers. More info
See in Glossary. This includes the first call stack depth of invocations from Unity’s native code into your scripting code, such as MonoBehaviour.Start
, MonoBehaviour.Update
, 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 CameraA component which creates an image of a particular viewpoint in your scene. The output is either drawn to the screen or captured as a texture. More info
See in Glossary through the Camera.main
API registers as a FindMainCamera
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.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.