Search Issue Tracker
By Design
Votes
0
Found in
2019.3.0a1
2019.3.0f2
Issue ID
1203358
Regression
Yes
[Performance Regression] Prefab PerformanceTest: MeasureSaveTimeForPrefab(20,1,1,1000) is significantly slower
The PrefabSaveTests test: Test: MeasureSaveTimeForPrefab(20,1,1,1000) is significantly slower in 2019.3 than 2019.2 or 18.4
It looks like the regression was introduced with the change-set: 2019.3.0a1 (25828b1b312)
There is a second, even worse regression introduced in 2020.1.a5 (1e4819d07b04)
Platform observed on - MacOS
To observe the issue:
https://observer.cds.internal.unity3d.com/afb89201c7d5c267b5743e5f7de3f8c2fd091ba0
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note (2019.3.X):
The regression with performance is due to the performance tests are leaking objects. If you run the performance test just one, v1 and v2 performance is similar. Asset db v1 runs a garbage collection during import and with v2 the garbage collection has been removed. In v2 we want the import to leave the loaded objects state the same before and after imports. By added a single clean up of objects (EditorUtility.UnloadUnusedAssetsImmediate();) in the test, the performance test runs much fast with v2.