Performance profiling in Unity - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is performance profiling in Unity?

Performance profiling in Unity is the process of measuring how your game uses resources like CPU, GPU, and memory to find parts that slow down the game or use too much power.

beginner

Name the main Unity tool used for performance profiling.

The main tool is the Unity Profiler, which shows detailed information about CPU, GPU, memory, rendering, and more while your game runs.

intermediate

What does the CPU Usage section in Unity Profiler show?

It shows how much time the CPU spends on different tasks like scripts, physics, rendering, and garbage collection, helping identify slow code parts.

intermediate

Why is garbage collection important in performance profiling?

Garbage collection frees unused memory but can cause pauses in the game. Profiling helps find when and how often it happens to reduce lag.

advanced

How can you reduce GPU bottlenecks found during profiling?

You can reduce GPU bottlenecks by optimizing shaders, lowering draw calls, simplifying models, and reducing screen resolution or effects.

Which Unity tool helps you analyze CPU and GPU usage during gameplay?

A Unity Profiler

B Unity Animator

C Unity Console

D Unity Package Manager

The Unity Profiler is designed to analyze CPU, GPU, memory, and other performance metrics during gameplay.

What does a high number of draw calls usually indicate?

A Efficient GPU usage

B Low memory usage

C Fast CPU processing

D Too many objects being rendered separately

Many draw calls mean the GPU must render many objects one by one, which can slow down performance.

What is a common cause of frame rate drops related to memory?

A Garbage collection running frequently

B Too few textures loaded

C Low CPU usage

D High screen resolution

Frequent garbage collection pauses the game to free memory, causing frame rate drops.

Which of these is NOT a Unity Profiler module?

A Rendering

B Animation

C Sound Mixer

D Physics

Unity Profiler does not have a 'Sound Mixer' module; sound is usually profiled with other tools.

How can you reduce CPU usage in Unity games?

A Add more lights

B Optimize scripts and reduce complex calculations

C Increase texture sizes

D Use more particle effects

Optimizing scripts and reducing heavy calculations lowers CPU load and improves performance.

Explain how you would use the Unity Profiler to find performance issues in a game.

Think about the steps from starting the profiler to spotting slow parts.

Describe common causes of performance problems in Unity games and how profiling helps fix them.

Consider what slows down games and how profiling points them out.

Practice

1. What is the main purpose of using performance profiling in Unity?

easy

A. To write story scripts for the game

B. To add new game features quickly

C. To find slow or heavy parts in your game code

D. To create game art and animations

Solution

1. Step 1: Understand performance profiling

   Performance profiling is used to check which parts of the game code take the most time or resources.

2. Step 2: Match purpose with options

   Only To find slow or heavy parts in your game code talks about finding slow or heavy parts, which matches the purpose of profiling.

3. Final Answer:

   To find slow or heavy parts in your game code -> Option C

4. Quick Check:

   Profiling purpose = find slow code [OK]

Hint: Profiling finds slow code parts to improve performance [OK]

Common Mistakes:

• Confusing profiling with adding features
• Thinking profiling creates art or story
• Mixing profiling with gameplay design

2. Which of the following is the correct way to mark a code section for profiling in Unity?

easy

A. Profiler.BeginSample("MyCode") and Profiler.EndSample()

B. Profiler.MarkStart("MyCode") and Profiler.MarkEnd()

C. Profiler.StartSample("MyCode") and Profiler.StopSample()

D. Profiler.Profile("MyCode")

Solution

1. Step 1: Recall Unity profiling API

   Unity uses Profiler.BeginSample and Profiler.EndSample to mark code sections.

2. Step 2: Compare options with correct API

   Only Profiler.BeginSample("MyCode") and Profiler.EndSample() matches the exact method names used in Unity.

3. Final Answer:

   Profiler.BeginSample("MyCode") and Profiler.EndSample() -> Option A

4. Quick Check:

   Correct API = BeginSample and EndSample [OK]

Hint: Use BeginSample and EndSample to mark profiling code [OK]

Common Mistakes:

• Using StartSample/StopSample instead of BeginSample/EndSample
• Using non-existent Profiler methods
• Forgetting to call EndSample after BeginSample

3. What will be the output in the Unity Profiler if you run this code snippet?

Profiler.BeginSample("HeavyTask");
for (int i = 0; i < 1000000; i++) { var x = Mathf.Sqrt(i); }
Profiler.EndSample();

medium

A. The Profiler shows a sample named 'HeavyTask' with time taken for the loop

B. The Profiler shows an error because of missing Profiler.StopSample()

C. No profiling data is recorded because Profiler.BeginSample is inside a loop

D. The Profiler shows a sample named 'HeavyTask' but with zero time

Solution

1. Step 1: Understand Profiler.BeginSample and EndSample usage

   The code marks the start and end of a heavy task loop, so the Profiler records the time spent inside.

2. Step 2: Analyze Profiler output

   The Profiler will show a sample named 'HeavyTask' with the time taken to run the loop, which is significant.

3. Final Answer:

   The Profiler shows a sample named 'HeavyTask' with time taken for the loop -> Option A

4. Quick Check:

   Profiler records marked code time = The Profiler shows a sample named 'HeavyTask' with time taken for the loop [OK]

Hint: Profiler shows time for code between BeginSample and EndSample [OK]

Common Mistakes:

• Confusing EndSample with StopSample
• Thinking profiler needs to be inside the loop
• Assuming profiler shows zero time for heavy code

4. Identify the error in this profiling code snippet:

Profiler.BeginSample("UpdateLoop");
UpdateGameObjects();
// Missing Profiler.EndSample()

medium

A. Profiler.BeginSample() should be called after UpdateGameObjects()

B. No error, the code is correct

C. Profiler.BeginSample() and EndSample() cannot be used in Update()

D. Profiler.EndSample() is missing, causing incorrect profiling data

Solution

1. Step 1: Check profiling code structure

   Profiler.BeginSample must be paired with Profiler.EndSample to mark the code section properly.

2. Step 2: Identify missing EndSample call

   The code is missing Profiler.EndSample(), which causes the Profiler to not close the sample and gives wrong data.

3. Final Answer:

   Profiler.EndSample() is missing, causing incorrect profiling data -> Option D

4. Quick Check:

   Missing EndSample causes profiling errors [OK]

Hint: Always pair BeginSample with EndSample to avoid errors [OK]

Common Mistakes:

• Forgetting to call EndSample after BeginSample
• Calling BeginSample after the code instead of before
• Thinking profiling can't be used in Update()

5. You want to profile two different parts of your game code separately: physics calculations and AI updates. How should you use the Profiler API to get clear timing for both?

hard

A. Call Profiler.BeginSample("Physics") once at game start and Profiler.EndSample() at game end, same for AI

B. Call Profiler.BeginSample("Physics") before physics code and Profiler.EndSample(), then Profiler.BeginSample("AI") before AI code and Profiler.EndSample()

C. Use Profiler.BeginSample("Physics") and Profiler.BeginSample("AI") at the same time without EndSample()

D. Only use Profiler.EndSample() after both physics and AI code without BeginSample()

Solution

1. Step 1: Understand separate profiling sections

   To profile two parts separately, you must mark each section with its own BeginSample and EndSample calls.

2. Step 2: Apply correct usage for both parts

   Call Profiler.BeginSample("Physics") before physics code and Profiler.EndSample(), then Profiler.BeginSample("AI") before AI code and Profiler.EndSample() correctly calls BeginSample and EndSample around physics code, then again around AI code, giving clear timing for each.

3. Final Answer:

   Call Profiler.BeginSample("Physics") before physics code and Profiler.EndSample(), then Profiler.BeginSample("AI") before AI code and Profiler.EndSample() -> Option B

4. Quick Check:

   Separate samples need separate BeginSample/EndSample pairs [OK]

Hint: Use separate BeginSample/EndSample pairs for each code section [OK]

Common Mistakes:

• Calling BeginSample once for whole game session
• Starting two samples without ending them
• Using EndSample without matching BeginSample