Search Unity

  1. Improved Prefab workflow (includes Nested Prefabs!), 2D isometric Tilemap and more! Get the 2018.3 Beta now.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. Let us know a bit about your interests, and if you'd like to become more directly involved. Take our survey!
    Dismiss Notice
  4. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice
  5. Want to see the most recent patch releases? Take a peek at the patch release page.
    Dismiss Notice

Profiler Overview page contains misleading information

Discussion in 'Documentation' started by Peter77, Apr 14, 2018.

  1. Peter77

    Peter77

    Joined:
    Jun 12, 2013
    Posts:
    2,635
    https://docs.unity3d.com/Manual/Profiler.html says:
    Profiling the game running in the editor is very inaccurate, as the editor comes with performance overhead. The editor also allocates a ton of garbage memory that is completely gone in a build. For example, GetComponent calls, where that Component is missing, allocates garbage memory in the editor, but it does not in a build.

    Therefore, this Profiler page is very misleading. People should profile a build running on the target device to get accurate results. Profiling the game running in the editor is misleading.

    This issue comes up a a lot in the Unity forums. People profile in the editor and wonder about these things. Then everybody responds with "Please profile a build, not the editor".

    In order to minimize this support overhead in the forums, could you please add something along the lines:
    "For accurate results on performance and memory, profile a build running on the target hardware." in big bold letters to the Profiler Overview page.

    Thank you.
     
    MartinTilo likes this.