Variables and serialization in Unity - Performance & Optimization

Performance: Variables and serialization

MEDIUM IMPACT

This concept affects how data is stored and loaded in Unity, impacting load times and memory usage during gameplay.

Saving and loading game state variables

Unity

[System.Serializable]
public class PlayerData {
    public int health;
    public string playerName;
    public List<Item> inventory;
}

// Using Unity's JsonUtility for serialization
string json = JsonUtility.ToJson(playerData);
File.WriteAllText(path, json);

JsonUtility is faster, produces smaller files, and can be used asynchronously to avoid blocking the main thread.

📈 Performance GainReduces blocking time to tens of milliseconds; smaller file size improves load speed.

Saving and loading game state variables

Unity

public class PlayerData {
    public int health;
    public string playerName;
    public List<Item> inventory;
}

// Using BinaryFormatter for serialization
BinaryFormatter bf = new BinaryFormatter();
FileStream file = File.Create(path);
bf.Serialize(file, playerData);
file.Close();

BinaryFormatter is slow, insecure, and produces large files; it also blocks the main thread during serialization.

📉 Performance CostBlocks main thread for hundreds of milliseconds on large data; large file size increases load time.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
BinaryFormatter serialization	N/A	N/A	N/A	[X] Bad
Unity JsonUtility serialization	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

Serialization affects the loading phase before rendering starts. Efficient serialization reduces the time spent reading and parsing data, allowing faster scene setup and rendering.

→Loading

→Memory Allocation

⚠️ BottleneckData parsing and file I/O during load

Optimization Tips

1Use Unity's JsonUtility for faster and smaller serialization.

2Avoid blocking the main thread by using asynchronous serialization.

3Minimize serialized data size to reduce load time and memory use.

Performance Quiz - 3 Questions

Which serialization method in Unity is generally faster and produces smaller files?

A Unity's JsonUtility

B BinaryFormatter

C XML serialization

D Manual byte array serialization

DevTools: Profiler

How to check: Open Unity Profiler, record while loading saved data, and check CPU usage and time spent in serialization functions.

What to look for: Look for long blocking times in serialization calls and high memory allocations during load.

Practice

1. What is the main purpose of serialization in Unity?

easy

A. To convert data into a format that can be saved or sent

B. To create new game objects during runtime

C. To increase the speed of the game

D. To change the color of game objects

Solution

1. Step 1: Recall the definition of serialization

   Serialization means converting data into a format that can be saved or sent.

2. Step 2: Match Unity's use of serialization

   Unity uses serialization to save game data or send it over networks.

3. Final Answer:

   To convert data into a format that can be saved or sent -> Option A

4. Quick Check:

   Serialization = convert data for saving/sending [OK]

Hint: Serialization means saving or sending data format [OK]

Common Mistakes:

• Confusing serialization with creating objects
• Thinking serialization changes game speed
• Mixing serialization with visual changes

2. Which of the following is the correct way to declare a public integer variable in a Unity C# script?

easy

A. int score public;

B. int public score;

C. public int score;

D. public integer score;

Solution

1. Step 1: Recall C# variable declaration syntax

   In C#, access modifier comes first, then type, then variable name.

2. Step 2: Check each option

   public int score; ('public int score;') follows correct order. Options A, B, C have wrong order or wrong type keyword.

3. Final Answer:

   public int score; -> Option C

4. Quick Check:

   Access modifier + type + name = correct declaration [OK]

Hint: Access modifier before type before name in C# [OK]

Common Mistakes:

• Putting 'public' after variable name
• Using 'integer' instead of 'int'
• Incorrect order of keywords

3. What will be the output of this Unity C# code?

using UnityEngine;

public class PlayerData {
    public string playerName = "Alex";
    public int level = 5;
}

public class Test : MonoBehaviour {
    void Start() {
        PlayerData data = new PlayerData();
        string json = JsonUtility.ToJson(data);
        Debug.Log(json);
    }
}

medium

A. Error: JsonUtility.ToJson requires MonoBehaviour

B. {"playerName":Alex,"level":5}

C. {"playerName":"Alex",level:5}

D. {"playerName":"Alex","level":5}

Solution

1. Step 1: Understand JsonUtility.ToJson output format

   JsonUtility converts object fields to JSON string with keys and values in quotes where needed.

2. Step 2: Check the JSON string format

   Strings have quotes, numbers do not. {"playerName":"Alex","level":5} matches correct JSON format with quotes around "Alex" and keys.

3. Final Answer:

   {"playerName":"Alex","level":5} -> Option D

4. Quick Check:

   JsonUtility outputs valid JSON string [OK]

Hint: JsonUtility outputs JSON with quotes around strings [OK]

Common Mistakes:

• Missing quotes around string values
• Using invalid JSON syntax
• Thinking JsonUtility needs MonoBehaviour object

4. Identify the error in this Unity C# code snippet:

using UnityEngine;

public class Player {
    public int score;
}

public class Game : MonoBehaviour {
    void Start() {
        Player player = new Player();
        string json = JsonUtility.ToJson(player);
        Debug.Log(json);
    }
}

medium

A. No error; code will output {"score":0}

B. Player class must inherit from MonoBehaviour to serialize

C. JsonUtility.ToJson requires static method call

D. score variable must be private to serialize

Solution

1. Step 1: Check if Player class can be serialized

   JsonUtility can serialize plain classes with public fields, no need to inherit MonoBehaviour.

2. Step 2: Check output of JsonUtility.ToJson

   Player's score defaults to 0, so JSON string will be {"score":0}.

3. Final Answer:

   No error; code will output {"score":0} -> Option A

4. Quick Check:

   Plain class with public fields serializes fine [OK]

Hint: Public fields in plain classes serialize without MonoBehaviour [OK]

Common Mistakes:

• Thinking class must inherit MonoBehaviour to serialize
• Assuming private fields serialize by default
• Believing JsonUtility requires static context

5. You want to save player settings including volume (float), username (string), and isFullScreen (bool) using Unity's JsonUtility. Which class definition correctly supports serialization of these variables?

hard

A. public class Settings { private float volume; private string username; private bool isFullScreen; }

B. public class Settings { [SerializeField] private float volume; [SerializeField] private string username; [SerializeField] private bool isFullScreen; }

C. public class Settings { protected float volume; protected string username; protected bool isFullScreen; }

D. public class Settings { public float volume { get; set; } public string username { get; set; } public bool isFullScreen { get; set; } }

Solution

1. Step 1: Understand JsonUtility serialization rules

   JsonUtility serializes public fields or private fields marked with [SerializeField] attribute.

2. Step 2: Evaluate each class definition

   public class Settings { protected float volume; protected string username; protected bool isFullScreen; } uses protected fields, which do not serialize. public class Settings { private float volume; private string username; private bool isFullScreen; } uses private fields without [SerializeField], so no serialization. public class Settings { [SerializeField] private float volume; [SerializeField] private string username; [SerializeField] private bool isFullScreen; } uses private fields with [SerializeField], which works. public class Settings { public float volume { get; set; } public string username { get; set; } public bool isFullScreen { get; set; } } uses properties, which JsonUtility does not serialize.

3. Step 3: Choose best practice

   Using private fields with [SerializeField] is recommended for encapsulation and serialization.

4. Final Answer:

   public class Settings { [SerializeField] private float volume; [SerializeField] private string username; [SerializeField] private bool isFullScreen; } -> Option B

5. Quick Check:

   Private fields + [SerializeField] serialize correctly [OK]

Hint: Use [SerializeField] for private variables to serialize [OK]

Common Mistakes:

• Assuming private fields serialize without attribute
• Using properties instead of fields for serialization
• Ignoring encapsulation best practices