Profile Android game performance in Godot with Arm Performance Studio
Introduction
Profile your Godot game with Arm Performance Studio
Install the Arm Performance Studio extension in Godot
Annotate Game Events for Profiling in Godot
Define performance regions in Godot
Use channels for threaded performance annotations
Create and track custom counters in Godot
Use custom activity maps in Godot profiling
Next Steps
Profile Android game performance in Godot with Arm Performance Studio
Introduction
Profile your Godot game with Arm Performance Studio
Install the Arm Performance Studio extension in Godot
Annotate Game Events for Profiling in Godot
Define performance regions in Godot
Use channels for threaded performance annotations
Create and track custom counters in Godot
Use custom activity maps in Godot profiling
Next Steps
Who is this for?
This is an introductory topic for Godot developers targeting Android devices who want to optimize game performance on Arm CPUs and Mali GPUs using Arm Performance Studio tools.
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Install the Arm Performance Studio Integration extension in Godot
- Annotate your Godot game with performance markers for profiling in Streamline and Performance Advisor
Prerequisites
Before starting, you will need the following:
- Familiarity with Godot
- Familiarity with Arm Performance Studio tools
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
PerformanceStudio.new() and call marker("Test"). If the project runs without script errors, the extension is available and your annotations can be captured.marker("Game Started") to emit a timestamped label. This label appears in the Streamline timeline for correlation with performance data.Region Start <name> and Region End <name> around the code of interest. Performance Advisor shows these regions on the frame rate analysis chart and in dedicated per‑region charts.