1000 Addressables.LoadAssetAsync calls, what is doing Addressables?

Consider that all asset bundles are part of the build and they are all local.

When I trigger 1000 Addressables.LoadAssetAsync calls that all point to different assets in different asset bundles, is Addressables loading all simultaneously, or is Addressables scheduling the work so that the IO system is not overwhelmed?

In what order are the async load calls processed when the total number of simultaneous load operations is limited? First-in, first-out?

Hey, good question. So, from 2021.1 on we use the AssetBundle.LoadFromFileAsync API to actually load the bundle. There is an async operation queue on the Engine side that handles these operations, and I believe they are handled FIFO, but I couldn’t say with 100% confidence. From there, the asset loads are going to be sync calls once the bundle is loaded.

1 Like