Search Issue Tracker
Won't Fix
Votes
0
Found in
5.5.2f1
Issue ID
900775
Regression
No
It is slower to load asset bundles from Cache than from Streaming Assets
How to reproduce:
1. Open the attached project
2. Play Test scene in editor
3. Press the button "Download from the Cache"
Result is around these values:
Loading Time was - 00 : 00 : 163
The Instantiate Time was - 00 : 00 : 15
4. Press the button "Download from Streaming Assets"
Result is around these values:
Loading Time was - 00 : 00 : 16
The Instantiate Time was - 00 : 00 : 12
One can notice that loading asset bundles from Streaming Assets is faster than from cache. The bundles are uncompressed for both cases.
Note: if you want to test on Android or iOS device, you should rebuild asset bundles. And move it from ProjectName/Build/android or ios/uncompressed/art to Streaming Assets/uncompressed
Results on Android device are same to the ones you see from editor.
Results on ios device are a bit different:
From cache:
Loading Time was - 00 : 00 : 334
The Instantiate Time was - 00 : 00 : 75
From Streaming Assets:
Loading Time was - 00 : 00 : 48
The Instantiate Time was - 00 : 00 : 37
Reproducible: 5.5.3f1, 5.6.0p1, 2017.1.0b1
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
With the current engine caching, there doesn't appear to be much we can do without pretty significant changes. Closing this for now.