Optimize Unity applications on Android using Neon intrinsics
Introduction
Set up
Arm Neon and the Unity Burst compiler
The sample project
The plain (unoptimized) code
The optimizations
Collecting performance data
Analyzing the performance data
Profiling best practice
Summary
Appendix
Next Steps
Optimize Unity applications on Android using Neon intrinsics
Review 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.
Open
Assets/BurstNeonCollisions/Scripts/CollisionCalculationScript.cs and change line 66 to public const Mode codeMode = Mode.Plain; to select the unoptimized mode for your initial measurements.From Window, select Packet Management > Package Manager. Set Packages to Unity Registry, search for Burst, select it, and select Install if it’s not already ticked.
To match the environment used in the Learning Path, use Unity v6.3 and Burst 1.8.28.
Review the character-wall and character-character collision functions. In Plain mode,
DoWallsPlain() loops through all characters and walls, while DoCharactersPlain() checks each character against the others; the code assumes a character can hit up to two walls.Burst can auto-vectorize your code efficiently, so hand-written Neon doesn’t always improve performance. Profile your app before and after adding Neon. If performance doesn’t improve, Burst might produce better-optimized code.