Skip to content

Unity Performance

App performance is critical for developers, particularly in VR, where poor performance can significantly impact user comfort.

Our SDK is designed to be resource-efficient while delivering robust analytics. We are continually optimizing to ensure it remains both lightweight and effective. For specific requirements, please contact us, and our customer success team will assist you.

Overall, the performance impact of our SDK is minimal compared to the demands of rendering and VR interaction systems. Recent performance test results are provided below.

Best Practices

  • Web requests can have a notable performance impact. If necessary, increase Automatic Send Timer to send fewer, larger requests.
  • Initializing a session should be done when the user is least likely to notice it - immediately when the application begins or during a scene load.
  • Prefer using IL2CPP over Mono if possible.

Performance Testing Overview

To provide comprehensive performance insights, we've tested our SDK with two different application profiles:

  1. Fantasy App - A single-scene mini game that represents a lightweight, focused VR experience. This test demonstrates SDK performance in simpler applications with minimal scene complexity.

  2. Demo App - A multi-scene simulation that represents practical real-world scenarios with more complex interactions, multiple scenes, and varied content. This test shows SDK performance in typical production environments.

These two test cases cover the spectrum of VR applications, from lightweight experiences to full-featured simulations, giving you a clear understanding of how our SDK performs across different use cases.

Test Device

All tests were conducted on the following device:

Meta Quest 3

  • CPU: Qualcomm Snapdragon XR2 Gen 2
  • RAM: 8 GB
  • GPU: Adreno 740

Methodology

All performance values were recorded using a custom lightweight performance profiler for Android devices, designed with minimal overhead to ensure accurate FPS and CPU usage readings.

For each test, we executed the app twice - once without the SDK to establish baseline performance, and once with our SDK included to determine the SDK's overhead.

Fantasy App Performance Test

Test Conditions

Test Setup

This was built on the Fantasy Sample scene with no major changes.

The SDK implementation included:

  • Gaze tracking
  • Controller interactions
  • 12 dynamic objects (including controllers)
  • 1 sensor value being written per frame (in addition to our default ones)
  • 1 custom event being written per second (in addition to our default ones)

Note

Recording a custom sensor every frame and a custom event every second far exceeds typical usage. These aggressive settings were intentional to stress-test the SDK as a worst-case scenario; real-world integrations would see even lower overhead.

Test Results

App without Cognitive3D App with Cognitive3D Relative % difference
Average framerate 68.72 fps 68.35 fps -0.54%
CPU usage (%) 53.84% 54.31% +0.87% (+0.47 percentage points)

Demo App Performance Test

Test Conditions

  • Date: February 2026
  • Unity SDK version: 2.2.0
  • Unity version: 2022.3.67f2
  • App: Cognitive3D Demo (multi-scene simulation) (available on the dashboard)

Test Setup

This test was conducted using the Cognitive3D Demo application, which includes multiple scenes and more complex real-world simulation scenarios.

The SDK implementation included:

  • Gaze tracking
  • Controller interactions
  • 25 dynamic objects in total across different scenes
  • 1 sensor value being written per frame (in addition to our default ones)
  • 1 custom event being written per second (in addition to our default ones)

Note

Recording a custom sensor every frame and a custom event every second far exceeds typical usage. These aggressive settings were intentional to stress-test the SDK as a worst-case scenario; real-world integrations would see even lower overhead.

Test Results

App without Cognitive3D App with Cognitive3D Relative % difference
Average framerate 70.48 fps 69.80 fps -0.96%
CPU usage (%) 54.68% 56.59% +3.49% (+1.91 percentage points)

intercom If you have a question or any feedback about our documentation please use the Intercom button (purple circle) in the lower right corner of any web page or join our Discord.