Using Neon intrinsics to optimize Unity on Android
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
Review
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

Capturing reliable performance data

Here are a few things you can do to improve the reliability of performance data you capture from the Profiler:

  1. Try to capture representative and repeatable captures

  2. Turn off performance scaling if you can (which may involve root permissions on your device) as the device may be varying the CPU frequency to adapt to varying loads and temperatures

  3. Use the same (or matching) device(s) when capturing and comparing multiple datasets

  4. Performance data can be logged outside of the Unity Editor - you can log data from within your own C# scripts

  5. Make use of profiling markers to highlight the code you want to measure in the Profiler and Analyzer

Back
Next