Asset bundles and optimization in Unity - Performance & Optimization

Performance: Asset bundles and optimization

HIGH IMPACT

This concept affects the initial load time and runtime memory usage by managing how game assets are loaded and unloaded.

Loading game assets efficiently

Unity

Use Asset Bundles to group related assets and load them asynchronously only when needed.

Reduces initial load time and memory by loading assets on demand.

📈 Performance GainNon-blocking load, reduces memory footprint, improves LCP.

Loading game assets efficiently

Unity

Load all assets at game start using Resources.Load for each asset individually.

Loads unnecessary assets upfront, increasing load time and memory usage.

📉 Performance CostBlocks rendering for several seconds on start, high memory consumption.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Load all assets at start	N/A	N/A	Blocks rendering for seconds	[X] Bad
Load asset bundles asynchronously	N/A	N/A	Non-blocking load, smooth rendering	[OK] Good

Rendering Pipeline

Asset bundles are loaded asynchronously, parsed, and then assets are instantiated in the scene, affecting loading and rendering stages.

→Loading

→Memory Allocation

→Rendering

⚠️ BottleneckLoading stage due to large asset size or synchronous loading calls.

Core Web Vital Affected

LCP

This concept affects the initial load time and runtime memory usage by managing how game assets are loaded and unloaded.

Optimization Tips

1Use asynchronous loading for asset bundles to avoid blocking the main thread.

2Group related assets into smaller bundles to load only what is needed.

3Avoid loading all assets at game start to reduce memory usage and improve load time.

Performance Quiz - 3 Questions

What is the main performance benefit of using asset bundles in Unity?

A Load assets asynchronously to reduce initial load time

B Increase asset size for better quality

C Load all assets at once to avoid delays

D Use Resources.Load for every asset

DevTools: Unity Profiler

How to check: Open Unity Profiler, record while loading assets, check CPU and Memory usage during asset load.

What to look for: Look for long blocking calls in CPU timeline and high memory spikes indicating inefficient asset loading.

Practice

1. What is the main benefit of using Asset Bundles in Unity?

easy

A. Automatically generate game scripts

B. Create UI elements faster

C. Improve physics calculations

D. Load game assets only when needed to save memory and download size

Solution

1. Step 1: Understand what Asset Bundles do

   Asset Bundles allow loading assets like textures, models, or sounds only when the game needs them, not all at once.

2. Step 2: Identify the main benefit

   This selective loading saves memory and reduces the initial download size of the game.

3. Final Answer:

   Load game assets only when needed to save memory and download size -> Option D

4. Quick Check:

   Asset Bundles optimize memory and size = B [OK]

Hint: Asset Bundles help load assets on demand, saving resources [OK]

Common Mistakes:

• Confusing Asset Bundles with script generation
• Thinking Asset Bundles improve physics
• Assuming Asset Bundles speed up UI creation

2. Which of the following is the correct way to load an Asset Bundle asynchronously in Unity?

easy

A. AssetBundle.LoadFromFileAsync(path)

B. AssetBundle.LoadFromFile(path)

C. AssetBundle.LoadAsync(path)

D. AssetBundle.LoadBundleAsync(path)

Solution

1. Step 1: Recall Unity's async Asset Bundle loading method

   The official method to load an Asset Bundle asynchronously from a file is AssetBundle.LoadFromFileAsync(path).

2. Step 2: Check other options for correctness

   LoadFromFile(path) is synchronous, LoadAsync(path) and LoadBundleAsync(path) do not exist in Unity API.

3. Final Answer:

   AssetBundle.LoadFromFileAsync(path) -> Option A

4. Quick Check:

   Async load method = LoadFromFileAsync [OK]

Hint: Async loading uses LoadFromFileAsync method exactly [OK]

Common Mistakes:

• Using synchronous LoadFromFile instead of async
• Choosing non-existent LoadAsync or LoadBundleAsync methods
• Confusing method names

3. Consider this code snippet in Unity:

var bundleRequest = AssetBundle.LoadFromFileAsync("Assets/Bundles/characters");
yield return bundleRequest;
var bundle = bundleRequest.assetBundle;
var prefab = bundle.LoadAsset<GameObject>("Hero");
Instantiate(prefab);

What happens when this code runs?

medium

A. Throws a compile-time error due to incorrect method usage

B. Loads the asset bundle synchronously and immediately instantiates 'Hero'

C. Loads the asset bundle asynchronously, then loads and instantiates the 'Hero' prefab

D. Loads the asset bundle but does not instantiate any prefab

Solution

1. Step 1: Analyze the async loading call

   AssetBundle.LoadFromFileAsync starts loading the bundle asynchronously, and yield return bundleRequest waits until loading finishes.

2. Step 2: Load asset and instantiate

   After loading, bundle.LoadAsset<GameObject>("Hero") loads the prefab named 'Hero', and Instantiate(prefab) creates it in the scene.

3. Final Answer:

   Loads the asset bundle asynchronously, then loads and instantiates the 'Hero' prefab -> Option C

4. Quick Check:

   Async load + instantiate prefab = C [OK]

Hint: Async load then yield before using asset bundle [OK]

Common Mistakes:

• Confusing async with sync loading
• Forgetting to yield before accessing assetBundle
• Assuming no instantiation happens

4. You wrote this code to unload an Asset Bundle after use:

bundle.Unload(false);

But memory usage stays high. What is the likely problem?

medium

A. Unload(false) unloads everything including assets, so code is correct

B. Unload(false) unloads only the bundle but keeps loaded assets in memory

C. You must call bundle.Dispose() instead of Unload()

D. Unload(false) causes a runtime error and stops unloading

Solution

1. Step 1: Understand Unload parameter meaning

   Unload(false) unloads the Asset Bundle but keeps all loaded assets in memory.

2. Step 2: Identify why memory stays high

   Since assets are still loaded, memory usage remains high until you unload assets or reload scene.

3. Final Answer:

   Unload(false) unloads only the bundle but keeps loaded assets in memory -> Option B

4. Quick Check:

   Unload(false) keeps assets loaded = A [OK]

Hint: Unload(true) frees assets too; false keeps them loaded [OK]

Common Mistakes:

• Assuming Unload(false) frees all memory
• Using Dispose() which doesn't exist for AssetBundle
• Thinking Unload(false) causes errors

5. You want to optimize your Unity game by loading only necessary assets at runtime and unloading them properly. Which approach best achieves this?

hard

A. Build asset bundles for groups of assets, load bundles asynchronously when needed, instantiate assets, then unload bundles with Unload(true) after use

B. Load all assets at game start synchronously, keep bundles loaded throughout gameplay

C. Use Resources.Load for all assets and never unload them

D. Build asset bundles but never unload them to avoid errors

Solution

1. Step 1: Identify best practice for asset loading

   Building asset bundles for logical groups and loading them asynchronously reduces initial load and keeps gameplay smooth.

2. Step 2: Proper unloading to free memory

   Unloading bundles with Unload(true) frees both the bundle and loaded assets, optimizing memory usage.

3. Final Answer:

   Build asset bundles for groups of assets, load bundles asynchronously when needed, instantiate assets, then unload bundles with Unload(true) after use -> Option A

4. Quick Check:

   Async load + proper unload = A [OK]

Hint: Async load bundles, instantiate assets, unload with true to free memory [OK]

Common Mistakes:

• Loading all assets at start wastes memory
• Using Resources.Load without unloading
• Never unloading bundles causes memory leaks