During 2017.2 beta, I posted some performance test results of mine:
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.
What the test is doing
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
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.
Raw Numbers
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.