We did some additional testing to try and find out how Addressables affect entering play mode.
We tested the same project on three computers, two PCs with identical hardware and a Mac.
This project has 104,976 assets in the AssetDatabase and 20,921 assets marked as addressable.
These times are how long it takes from pressing play until the splash screen in our project loads.
We used unity 2019.3.0f3 for all tests.
Here are the baseline times (in seconds) without the Addressables package installed:
PC1: 7.55, 6.68, 5.56
PC2: 6.15, 6.11, 6.03
Mac: 8.40, 8.34, 8.31, 8.45
With Addressables v1.1.10 installed here are the times with the fast play mode script selected:
PC1: 21.35, 15.45, 16.09
PC2: 17.35, 21.10, 21.90
Mac: 24.96, 21.47, 22.01, 21.89
Here are the times with the virtual play mode script selected:
PC1: 60.06 (error), 10.64 (error)
Here are the times with the package play play mode script selected:
PC1: 8.14, 8.12, 8.08
PC2: 18.53, 16.01, 15.95
We repeated the same tests with Addressables v1.5.1 installed.
Here are the times with use asset database play mode script selected:
PC1: 17.02, 14.45, 14.38
PC2: 23.89, 23.43, 22.86
Mac: 18.73, 18.14, 17.97, 18.53
Here are the times with the simulate groups play mode script selected:
PC1: 600+ (gave up)
Here are the times with the use existing build play mode script selected:
PC1: 7.05, 10.14. 7.23
PC2: 19.04, 16.44, 16.24
Mac: 10.74, 10.25, 9.95, 9.85
I would like to reiterate austin-beck’s requests for information.
The amount of time the Addressables package adds to entering play is a tough pill to swallow.
Are there any other projects where people are running into performance issues with addressables and a large number of assets?
Does unity intend to improve performance when addressables are paired with a large number of assets?