Search Unity

  1. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Performance Overview

Discussion in '2017.3 Beta' started by Peter77, Oct 25, 2017.

  1. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,574
    During 2017.2 beta, I posted some performance test results of mine:
    https://forum.unity.com/threads/overall-performance-degredation-in-2017-2.497193/

    I thought I'm going to continue it and run the same test(s) with 2017.3.

    Overall, 2017.3.0b6 is the fastest 2017.x build with my project. According to my tests, especially some performance "spikes" are flattened now, compared to 2017.1 and 2017.2.

    The (first-person) game I'm working on features an automated performance test. It works like this:
    • Camera is placed at a defined position in the scene
    • Camera makes a 360 degree rotation around the Y-axis within 20 seconds (slowly rotating around y)
    • Every second the test captures the average CPU frame time of the last second
    The game runs just like it would normally do, but the camera/player does not move and the AI in unable to see the player.

    I ran this test with three different builds (Standalone Windows 64bit):
    • 2017.1.1p3
    • 2017.3.0b6 without any modifications
    • 2017.3.0b6 with Physics.autoSyncTransforms=false, Physics2D.autoSyncTransforms=false, Physics2D.autoSimulate=false

    unity2017_3_0b6_scene_4_3.png unity2017_3_0b6_scene_5_4.png unity2017_3_0b6_scene_6_8.png

    The last test "SCENE_6_8" runs partly about 0.5ms slower than 2017.1, but the total peak is much lower. Here are the actual samples for that test, numbers are in milliseconds.
    Code (CSharp):
    1. 2017.1.1p3  2017.3.0b6  2017.3.0b6 – AutoSync=off
    2. 5.66558     6.134033    5.793048
    3. 6.329998    6.561479    6.143956
    4. 6.763355    6.734349    6.347656
    5. 7.452619    6.893628    6.488628
    6. 8.090112    6.950378    6.574244
    7. 8.312887    6.942854    6.594206
    8. 7.5344      6.804382    6.347656
    9. 6.97581     6.724518    6.249848
    10. 6.462638    6.662937    6.253052
    11. 5.953998    6.451729    6.102027
    12. 5.657993    6.299289    5.893124
    13. 5.458666    6.08354     5.751336
    14. 5.532955    6.034391    5.62895
    15. 5.652476    5.952381    5.474487
    16. 5.764665    5.988755    5.338628
    17. 5.771681    5.819631    5.308444
    18. 5.707481    5.762561    5.378313
    19. 5.607051    5.748466    5.414643
    20. 5.584717    5.964733    5.598867
    21. 5.605005    6.08576     5.724749
     
  2. PhilSA

    PhilSA

    Joined:
    Jul 11, 2013
    Posts:
    1,926
    Awesome results! Very reassuring
     
  3. laurentlavigne

    laurentlavigne

    Joined:
    Aug 16, 2012
    Posts:
    6,147
    Send this man a complete Unity Beta leisure suit!
    Your tests are play mode, how is it to use the editor? In b1 I noticed that compile time was slower and general use was a bit glitchy.
     
  4. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,574
    I was running the tests in a build. I didn't spend much time with the editor yet.

    I still use 2017.1 to work on the project. I only open copies of it in 2017.2 and 2017.3 to check for issues and run the performance test.
     
    Prodigga likes this.