Application Performance Analysis


All Oculus Quest developers MUST PASS the concept review prior to gaining publishing access to the Quest Store and additional resources. Submit a concept document for review as early in your Quest application development cycle as possible. For additional information and context, please see Submitting Your App to the Oculus Quest Store.

We're no longer accepting submission of 32-bit Oculus Quest apps. Any new or updated Oculus Quest application needs to be 64-bit. Please contact Oculus if you are unable to comply with this policy. Oculus Go and Gear VR apps will not be affected by this change.

To distribute your Quest app in the Oculus store, your app must meet performance requirements. As a result, you should understand what affects your app’s performance and how to evaluate it.

For a discussion on mobile latency on Oculus devices and how the CPU and GPU synchronize to render frames, see Gameplay Latency for Oculus Quest, Oculus Go and Gear VR (blog post). For more information on Asynchronous TimeWarp, which helps reduce rendering latency, see Asynchronous TimeWarp.

In addition, see the following topics for analysis tools and examples.

Tools for Performance Analysis

  • Logcat for Basic Performance Stats
    A simple way to get some basic performance numbers is to use logcat with a filter for VrApi.
  • SysTrace Profiler Tool
    SysTrace can record detailed logs of system activity that can be viewed in the Google Chrome browser.
  • Snapdragon Profiler Tool
    The Qualcomm Snapdragon Profiler allows developers to analyze performance on Android devices with Snapdragon processors over USB, including CPU, GPU, memory, power, and thermal performance.
  • OVR Metrics Tool
    Describes how to install and use the OVR Metrics Tool for evaluating frame rate, heat, and GPU and CPU performance.

Performance Analysis Examples

The following topics show the effect of different parameters on app performance.