Search Issue Tracker
Duplicate
Duplicate in 2019.3
Votes
2
Found in
2019.3.0a1
2019.3.0a8
Issue ID
1171423
Regression
Yes
AssetDatabase.Refresh() executes slower when compared to previous versions
How to reproduce:
1. Open the attached project("AssetImportPerformance")
2. Go to BugReport > Create 100 assets
3. Observe console
Expected result: AssetDatabase.Refresh takes around the same amount of time regardless of Unity versions
Actual result: AssetDatabase.Refresh takes more time than in previous versions
Reproducible with: 2019.3.0a1, 2019.3.0a11
Not reproducible with: 2017.4.30f1, 2018.4.5f1, 2019.1.12f1, 2019.2.0b10
Note:
- It seems to reproduce only on HDD hard drives. Storing project in SSD hard drive results in expected behaviour even in 2019.3.0a1 and above.
-
Fernando-Ferreira
Jul 25, 2020 02:33
Unity 2020.1 still having this issue
-
phanemy
Oct 31, 2019 09:12
I find this kind of behaviour too, my custom importer for 3Dtiles files, importing one big file take 3 minutes with version 1, now with the new version it take 18 min
-
Peter77
Jul 24, 2019 12:43
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
- [Search] Index Manager: Empty item in Include or Exclude list will be taken in count
- [Search] Index Manager folder browse button is limited to Asset folder
- [Search] User Created Indices disappear from manager list if disabled
- [macOS] Crash on GC_mark_from when trashed GC objects are used by Burst
- Shadows are not casted when you first Blit the Shadow map and then set it back to Buffer
This is a duplicate of issue #1171344