Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.4.29f1
2019.4
2021.1
2021.2
Issue ID
1292657
Regression
No
[iOS] Physics.Proccesing is causing performance spikes
Reproduction steps:
1. Open project in "Level1.zip"
2. Open Scene "Terrain1_1"
3. Build for iOS and Deploy the application to a device
4. In Editor open Profiler window (ctrl/cmd + 7)
5. Inspect the CPU usage for your iOS device
Expected behaviour: CPU usage is consistent
Actual behaviour: Physics.Processing causes extreme spikes in performance (Up to 200 ms at times)
Reproducible with: 2019.4.30f1, 2019.4.17f1, 2021.1.0b1, 2021.2.0a1
Not reproducible with 2020.2.2f1
Devices tested (view profiler images for devices below):
Reproducible:
VLNQA00204 iPhone 5C (iOS 10.3.3) reproduced with 2018.4.30f1, 2019.4.17f1
iPhone 6 (iOS 12.4.8) reproduced with 2021.1.0b1, 2021.2.0a1, couldn't reproduce with 2020.2.2f1
Not reproducible:
VLNQA00310 iPad Pro 12.9 1st gen (iOS 13.4.1) (there are some spikes in physics, but nothing that would change the overall FPS)
iPhone 6s (iOS 13.3.1)
iPhone 12 Pro (iOS 14.2.1)
iPhone 7 (iOS 12.3.1)
iPhone 12 mini (iOS 14.1)
VLNQA00339, Lge LG V50 ThinQ 5G (LM-V500N), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
VLNQA00024, Xiaomi Mi 5 (MI 5), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
Note: Images of CPU loads from profiler should be inspected as there are physics spikes in some devices but they do not cause the overall performance to decrease
-
studentvz
Feb 11, 2021 17:44
Thread with more details about this regression.
https://forum.unity.com/threads/unity-performance-regressions-cpu-usage-physics-proccesing-rendering-spikes-and-more.1056236
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (2021.2.X):
The spikes are a side effect of physics thread having to wait on weaker devices. Those spikes do not affect performance and give false increased reading by including thread wait time, which we can do nothing about due to weaker device hardware.
Existing performance issues are caused by either scripting or rendering. To better observe spikes reported by scripting/rendering, physics graph can be turned off by clicking "Physics" label on left side of profiler graph.