Performance

Introduction

For accounting the performance of the Holoscan Sensor Bridge, we want to qualify the computational resources spent by the Holoscan Software while measuring the glass-to-glass latency.

Currently, the Holoscan Sensor Bridge is compatible with the NVIDIA Jetson Orin AGX and NVIDIA Orin IGX. We are going to cover the Jetson Orin AGX.

Jetson Orin AGX Performance

Setup

The Holoscan Sensor Bridge is connected as specified in the Holoscan Sensor Bridge/Hardware Connection using a 10Gbit/s ethernet connection.

Initial Clarifications

We are running the application as specified in the Holoscan Sensor Bridge/Running the Demo. We use the unaccelerated version of the IMX274 example given that the Jetson Orin AGX does not support DPDK^[1]. It uses UDP communication over Ethernet for the Holoscan Sensor Bridge - Jetson communication. The results might dramatically change for the NVIDIA Orin IGX platforms provided they support NVIDIA ConnectX expansion cards for network communication.

Results

Please, find the results for the Jetson Orin AGX below.

Sensor	Image Dimensions (px)	CPU Usage (%)	RAM Usage (MiB)	GPU Usage (%)	Glass-to-Glass Latency (ms)
IMX274	3840x2160 (4K)	2.56 (total) 30.6 (core)	347	14	64

A second camera captured the glass-to-glass latency using video mirroring (sensor capturing at a screen with a timer). The (total) CPU usage represents the percentage of the entire CPU, whereas the core is the use percentage of relative to a single CPU core.

Note: We are currently working on expanding the sensor list. Stay tuned!