Search Unity

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

Performance Overview

Discussion in '2018.2 Beta' started by Peter77, Apr 21, 2018.

  1. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,574
    Today I ran the automated performance test of my game with Unity 2018.2.0b1 and present the results below, just like I did before, during older beta cycles:
    1. Unity 2017.2 Performance Overview
    2. Unity 2017.3 Performance Overview
    3. Unity 2018.1 Performance Overview

    2018.2.0b1 is slower than 2018.1.0b9, but faster than Unity 2017.x with my project. 2018.2.0b1 performs about 0.7ms slower than 2018.1 in some cases.

    I haven't looked into what exactly is causing this performance difference yet.

    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.

    It measures the "base-line" of the game so to speak. If an actual gamer plays the game, more things are going to happen, which is missing in the test, such as visual and sound effects when firing weapons, additional AI to hunt the player and more navigation pathing.

    I run this test in a Standalone Windows 64bit (Mono) Player. The following Physics settings are applied:
    • Physics.autoSyncTransforms=false
    • Physics.autoSimulate=true
    • Physics2D.autoSyncTransforms=false
    • Physics2D.autoSimulate=false

    The y-axis represents the average CPU time in milliseconds, how long "one frame took". The x-axis represents the sample points while the camera makes its 360° rotation. Each test runs for 20 seconds, one sample every second, thus 20 samples for each test. Fewer milliseconds (vertical axis) indicate better performance.
    all_4_3.png

    all_5_4.png

    all_6_8.png
     
    Deeeds, PhilSA and optimise like this.
  2. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,574
    The following images provide a 2018.x only comparison...

    2018_4_3.png

    Code (CSharp):
    1. 2018.2.0b1   2018.1.0b9
    2. 3.918648   4.012695
    3. 3.813885   3.900313
    4. 3.779804   3.795971
    5. 3.922287   3.709807
    6. 4.250995   4.006592
    7. 4.578473   4.225333
    8. 4.731088   4.351807
    9. 4.880133   4.479545
    10. 4.801043   4.462891
    11. 4.632173   4.358706
    12. 4.305729   4.357379
    13. 4.117989   4.013672
    14. 3.886851   3.73567
    15. 3.754462   3.630707
    16. 3.710033   3.566973
    17. 3.725187   3.571969
    18. 3.713424   3.722918
    19. 3.798514   3.839369
    20. 3.928271   3.988441
    21. 3.931622   4.010742
    22.  

    2018_5_4.png

    Code (CSharp):
    1. 2018.2.0b1   2018.1.0b9
    2. 5.534304   5.130083
    3. 5.555885   5.197792
    4. 5.665580   5.214056
    5. 5.630322   5.230586
    6. 5.716378   5.259888
    7. 5.628264   5.233765
    8. 5.629636   5.204117
    9. 5.746373   5.378969
    10. 5.710255   5.306506
    11. 5.703319   5.285645
    12. 5.635808   5.206014
    13. 5.556560   5.133213
    14. 5.548467   5.163448
    15. 5.551839   5.131335
    16. 5.494505   5.069001
    17. 5.526029   5.093492
    18. 5.562337   5.17037
    19. 5.576579   5.221049
    20. 5.599549   5.157785
    21. 5.595458   5.192732


    2018_6_8.png

    Code (CSharp):
    1. 2018.2.0b1    2018.1.0b9
    2. 6.218762    5.59404
    3. 6.468152    5.880328
    4. 6.625750    6.152416
    5. 7.031421    6.363326
    6. 6.901989    6.367146
    7. 6.911705    6.321643
    8. 6.650002    6.180969
    9. 6.568659    5.970523
    10. 6.455642    5.881382
    11. 6.211180    5.717752
    12. 6.070224    5.560684
    13. 5.907485    5.481709
    14. 5.814922    5.362904
    15. 5.594776    5.221824
    16. 5.462646    5.107677
    17. 5.390782    5.097229
    18. 5.510602    5.064666
    19. 5.581326    5.181723
    20. 5.793048    5.321087
    21. 5.920771    5.457712
     
    Last edited: Apr 21, 2018
    Igualop, Deeeds and luispedrofonseca like this.
  3. xCyborg

    xCyborg

    Joined:
    Oct 4, 2010
    Posts:
    631
    Can you add in the LTS version?
     
    JamesArndt likes this.
  4. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,574
    I just profiled 2017.4.1f1. It's pretty similar to the 2017.3.0b6 results. I will include 2017.4 in the overview graphs next time.
     
  5. laurentlavigne

    laurentlavigne

    Joined:
    Aug 16, 2012
    Posts:
    6,147
    Not bad for a first beta.
     
  6. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,127
    I'm curious about what you'll find.
     
    hippocoder likes this.
  7. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,574
  8. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,574
    Today I repeated the test with Unity 2018.2.0f1 (Release Candidate 1). Unfortunately, 2018.2 continues to be slower than 2018.1 with my project, about 0.5ms by average.

    2018_2_0f1_scene_4_3.png

    2018_2_0f1_scene_5_4.png

    2018_2_0f1_scene_6_8.png