Search Issue Tracker

Fixed in 2018.2.X



Found in



Issue ID




[iOS] Performance regression on iOS introduced in 2017.3.0 alpha



Reproduction Steps:
1. Open User's project
2. Build for iOS (development build)
3. Deploy to an iOS device
4. Attach Unity profiler
5. Notice the difference in CPU usage

Approximate test results:
Unity 2017.1.3f1 - CPU ~2.3 ms
Unity 2017.2.1p4 - CPU ~2.3 ms
Unity 2017.3.0a1 - CPU ~6.8 ms
Unity 2017.3.0a4 - CPU ~6.5 ms
Unity 2017.3.0a5 - CPU ~33.3 ms
Unity 2017.3.0p3 - CPU ~33.3 ms
Unity 2018.1.0b4 - CPU ~33.2 ms

Expected Behaviour: Similar CPU/GPU with different Unity versions.

Good performance: Unity 2017.1.3f1, 2017.2.1p4
Worse performance: Unity 2017.3.0a1, 2017.3.0a4
Current performance: Unity 2017.3.0a5, 2017.3.0p4, 2018.1.0b4

Reproduced on device: iPhone 7 Plus iOS 10.3.2

Comments (1)

  1. PolyVector

    May 23, 2018 18:34

    Any chance this will be resolved in the LTS stream? This bug is driving me absolutely crazy.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.