Search Issue Tracker
Duplicate
Votes
1
Found in
2020.1.0b14
2020.2.0b9
2021.1
Issue ID
1290128
Regression
Yes
[Mobile] Resources.Load performance regression when (LZ4/LZ4HC) Compression is applied
How to reproduce:
1. Open the attached "resources-load-slow.zip" Project
2. Build it on the trunk and run It on an android device
3. Note the time
4. Build the project on the 2019.4 version
5. Compare the time
Expected behavior: Resources.Load takes the same amount of time on every version
Actual behavior: Resources.Load takes longer on 2020 versions than 2019
Reproducible with: 2020.1.0b14, 2020.1.14f1, 2020.2.0b11, 2021.1.0a5
Not reproducible with: 2018.4, 2019.4, 2020.1.0b13
Reproducible devices:
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00313, Huawei Y6 Ⅱ Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00310 iPad Pro 12.9 1st gen (iOS 13.4.1)
Note:
- Seems to only be reproducible on mobile devices. Windows standalone did not reproduce the issue.
- Not reproducible with default compression
- With better devices, the regression is not so much visible
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
This is a duplicate of issue #1287839