# Orin NX performance issue

**URL:** <https://forums.developer.nvidia.com/t/orin-nx-performance-issue/244303>\
**Category:** DeepStream SDK\
**Created:** [February 27, 2023, 11:25pm UTC](https://forums.developer.nvidia.com/t/orin-nx-performance-issue/244303 "2023-02-27T23:25:06Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![deveso](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@deveso](https://forums.developer.nvidia.com/u/deveso)\
**Post date:** [February 27, 2023, 11:25pm UTC](https://forums.developer.nvidia.com/t/orin-nx-performance-issue/244303/1 "2023-02-27T23:25:06Z")

</div>

I have a Jetson Xavier NX 8GB with Deepstream 6.0 running at 110fps with the YoloV3 example. For comparison, I have a new Jetson Orin NX 16GB with Deepstream 6.2. However, this only manages 52fps with exactly the same settings. The Xavier NX has already installed the patch [Deepstream 6 YOLO performance issue - #9 by adventuredaisy](https://forums.developer.nvidia.com/t/deepstream-6-yolo-performance-issue/194238/9) . I think Deepstream 6.2 is also already patched. Why does the Orin NX perform so poorly? I would have expected a much higher performance from the device. DLA1 and DLA2 are not active.

**• Hardware Platform (Jetson / GPU)** Jetson Orin NX 16GB  
**• DeepStream Version** Deepstream-6.2  
**• JetPack Version (valid for Jetson only)** Jetpack 5.1  
**• TensorRT Version** 5.1  
**• OpenCV** without CUDA

**• Hardware Platform (Jetson / GPU)** Jetson Xavier NX 8GB  
**• DeepStream Version** Deepstream-6.0  
**• JetPack Version (valid for Jetson only)** Jetpack 4.6  
**• TensorRT Version** 8.0.1.6  
**• OpenCV** without CUDA

---

<div class="post-metadata">

**Author:** ![Fiona.Chen](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/fiona.chen/32/15508_2.png) [@Fiona.Chen](https://forums.developer.nvidia.com/u/Fiona.Chen)\
**Post date:** [February 28, 2023, 2:26am UTC](https://forums.developer.nvidia.com/t/orin-nx-performance-issue/244303/3 "2023-02-28T02:26:25Z")

</div>

Have you disabled the power save mode of Orin before you tested the Orin performance? [Jetson Orin NX Series and Jetson AGX Orin Series — Jetson Linux  
Developer Guide 34.1 documentation (nvidia.com)](https://docs.nvidia.com/jetson/archives/r35.1/DeveloperGuide/text/SD/PlatformPowerAndPerformance/JetsonOrinNxSeriesAndJetsonAgxOrinSeries.html#jetson-agx-orin-series)

You can also use this method to enable the max clock: [VPI - Vision Programming Interface: Performance Benchmark (nvidia.com)](https://docs.nvidia.com/vpi/algo_performance.html#maxout_clocks)

---

<div class="post-metadata">

**Author:** ![adventuredaisy](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/adventuredaisy/32/77196_2.png) [@adventuredaisy](https://forums.developer.nvidia.com/u/adventuredaisy)\
**Post date:** [February 28, 2023, 3:44am UTC](https://forums.developer.nvidia.com/t/orin-nx-performance-issue/244303/4 "2023-02-28T03:44:18Z")

</div>

Ullrichthomas92  
What is the carrier board you are using for the Orin NX 16GB.  
Are you using the deepstream “objectDetector\_yolo” example  
for your test?

---

<div class="post-metadata">

**Author:** ![deveso](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@deveso](https://forums.developer.nvidia.com/u/deveso)\
**Post date:** [February 28, 2023, 8:24am UTC](https://forums.developer.nvidia.com/t/orin-nx-performance-issue/244303/5 "2023-02-28T08:24:07Z")

</div>

Yes, the Jetson is running at maximum power. Jetson\_clocks is active and NVP model 0 at MAXN. The Jetson consumes almost 25W when I run deepstream. So that shouldn’t be the problem.

@adventuredaisy I’ve been following your work for a while. You already have experience with the performance of Xavier and Orin. Can you maybe share some information? With your Xavier NX you get up to 55fps with Yolo. What performance can be expected with your Orin dev kit with the same configuration? Did you get your Yolo model up and running with DLA support?

I developed my own carrier board. However, I am currently using the Xavier NX dev kit to compare both devices. Yes I use the objectDetector\_Yolo example with deepstream\_app\_config\_yoloV3.txt

---

<div class="post-metadata">

**Author:** ![Fiona.Chen](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/fiona.chen/32/15508_2.png) [@Fiona.Chen](https://forums.developer.nvidia.com/u/Fiona.Chen)\
**Post date:** [February 28, 2023, 10:06am UTC](https://forums.developer.nvidia.com/t/orin-nx-performance-issue/244303/6 "2023-02-28T10:06:55Z")

</div>

I tested with my Orin Nano 8GB board with DeepStream 6.2, the sample of /opt/nvidia/deepstream/deepstream-6.2/sources/objectDetector\_Yolo/deepstream\_app\_config\_yoloV3.txt performance is about 104 FPS with fakesink. Orin NX should be better than Orin Nano.

Please check your settings. You need to disable the clock gating with the script here : [VPI - Vision Programming Interface: Performance Benchmark (nvidia.com)](https://docs.nvidia.com/vpi/algo_performance.html#maxout_clocks)

---

<div class="post-metadata">

**Author:** ![deveso](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@deveso](https://forums.developer.nvidia.com/u/deveso)\
**Post date:** [February 28, 2023, 2:02pm UTC](https://forums.developer.nvidia.com/t/orin-nx-performance-issue/244303/7 "2023-02-28T14:02:15Z")

</div>

I found the mistake. I moved objectDetector\_Yolo example to another directory without recompiling it. Performance is now at 180fps with fakesink. Thanks

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\
**Post date:** [March 14, 2023, 2:02pm UTC](https://forums.developer.nvidia.com/t/orin-nx-performance-issue/244303/8 "2023-03-14T14:02:32Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
