Adding and removing components in Unity - Performance & Optimization

Performance: Adding and removing components

MEDIUM IMPACT

This affects frame rendering speed and responsiveness by changing the number of active components on GameObjects during gameplay.

Dynamically adding or removing components during gameplay

Unity

void Start() {
  cachedRigidbody = gameObject.GetComponent<Rigidbody>();
}

void ToggleRigidbody(bool enable) {
  if (enable && cachedRigidbody == null) {
    cachedRigidbody = gameObject.AddComponent<Rigidbody>();
  } else if (!enable && cachedRigidbody != null) {
    Destroy(cachedRigidbody);
    cachedRigidbody = null;
  }
}

Add or remove components only when necessary and cache references to avoid repeated costly calls.

📈 Performance GainReduces CPU spikes by limiting component changes to explicit events, not every frame.

Dynamically adding or removing components during gameplay

Unity

void Update() {
  if (Input.GetKeyDown(KeyCode.Space)) {
    gameObject.AddComponent<Rigidbody>();
  }
  if (Input.GetKeyDown(KeyCode.Backspace)) {
    Destroy(gameObject.GetComponent<Rigidbody>());
  }
}

Adding or removing components inside Update causes frequent CPU spikes and possible frame drops.

📉 Performance CostTriggers multiple script recompilations and internal Unity overhead per frame when keys are pressed.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Add/remove components every frame in Update	Many component adds/removes	Multiple script recompilations	High CPU usage	[X] Bad
Add/remove components on explicit events with caching	Few component changes	Single script recompilation per event	Low CPU usage	[OK] Good

Rendering Pipeline

Adding or removing components affects the scripting and physics update stages, causing Unity to recompile scripts and update internal component lists.

→Script Execution

→Physics Update

→Garbage Collection

⚠️ BottleneckScript Execution due to component initialization and destruction overhead

Core Web Vital Affected

INP

This affects frame rendering speed and responsiveness by changing the number of active components on GameObjects during gameplay.

Optimization Tips

1Avoid adding or removing components inside Update or other frequent loops.

2Cache component references to minimize repeated GetComponent calls.

3Batch component changes and trigger them only on explicit gameplay events.

Performance Quiz - 3 Questions

What is the main performance cost of adding components every frame in Unity?

A Frequent script recompilation and CPU spikes

B Increased GPU load

C More memory allocated for textures

D Slower network communication

DevTools: Unity Profiler

How to check: Open Unity Profiler, record gameplay, filter by 'Scripts' and 'GC', look for spikes during component add/remove calls

What to look for: High spikes in CPU usage and garbage collection during component changes indicate performance issues