Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.5.2f1
Issue ID
900796
Regression
No
[Android] Downloading from the cache by Unity Web Request is slower than by WWW
How to reproduce:
1. Open the attached project
2. Open Test2 scene
3. Build and run Test2 scene on Android device
4. Press the button "Download from the Cache by UWR"
Result is around these values:
Loading Time was - 00 : 00 : 329
The Instantiate Time was - 00 : 00 : 76
5. Press the button "Download from the Cache by WWW"
Result is around these values:
Loading Time was - 00 : 00 : 168
The Instantiate Time was - 00 : 00 : 57
One can notice that loading asset bundles from cache by Unity Web Request is slower than by WWW. The bundles are uncompressed for both cases.
Note: I haven't been able to reproduce it in editor
DUT(reproducible):
LG G5 [LG-H850], Qualcomm Snapdragon 820, Adreno 530, OS 6.0.1
Reproducible: 5.5.3f1, 5.6.0p1
Not reproducible: 2017.1.0b1
Not reproducible: For reliable measurement both WWW and UnityWebRequest should be used at least once before starting measurement
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment