How can addressables be optimized for large-scale mobile games to improve memory management and loading times?
Optimize the assets inside, how you distribute them among addressables, and when you load and release them.
One particularly nasty thing is releasing all addressable content and then loading another addressable which contains mostly the same content. This forces an unnecessary reload. But that’s about it from what I recall. Everything else is on a per-case basis.
There’s no silver bullet, no magic trick here. Addressables are containers, much like a zip file. You can’t “optimize” the container itself.
Use the profiler to determine what your issue is and try to fix that. Is it memory management? Then maybe you need more fine-grained bundles. Is it loading time? Then bigger addressables will likely be more efficient. But most of all: optimize the assets. “Smaller” assets use less memory and load faster.
I recalled there was this best practices blog post: Addressables: Planning and best practices
It does point out that there will be project-specific tradeoffs to be made. Follow the cheat sheets linked at the bottom.
Thanks a bunch 