AGX ORIN - consuming more power in 15w mode in Benchmarking process with trtexec tool

Hello,

I tried to benchmark yolov3 network with trtexec tool in 15W mode as GPU as target device
I have observed the mean power consumption with the help tegrastats api log during the benchmarking process. The avg power consumption was 30w which is over15w,

Power rail Watts
VDD_CPU_CV 1.07
VDD_GPU_SOC 20.62
VIN_SYS_5V0 6.69
VDDQ_VDD2_1V8AO 2.32

Board Config:

NVIDIA Jetson AGX Orin
L4T 35.1.1 [ JetPack CUDA-X AI developer preview ]
Ubuntu 20.04.5 LTS
Kernel Version: 5.10.104-tegra
CUDA 11.4.239
CUDA Architecture: NONE
OpenCV version: 4.5.4
OpenCV Cuda: NO
CUDNN: 8.5.0.87
TensorRT: 8.5.0.4
Vision Works: NOT_INSTALLED
VPI: NOT_INSTALLED
Vulcan: 1.3.203

Hi,

Thanks for opening this issue.

We are trying to reproduce this internally and check with our internal team.
Will share more information with you later.

Hi,

We want to confirm the software you use again.
For JetPack 5.0.2, do you use cuDNN 8.4.1 and TensorRT 8.4.1?

We test trtexec with the ResNet50 model under 15W and cannot reproduce the 20W VDD_GPU_SOC result.
Does it only happen on the YOLOv3 network? If yes, could you share the model you used with us?

Thanks.

Hi AastaLLL,

Thanks for checking,

I have used the Developer preview Jetpack which has

CUDNN: 8.5.0.87
TensorRT: 8.5.0.4

I have tried the Resnet50 also, here the VDD_GPU_SOC is under 15W, but the total module power was 20W.

Power(watt)
VDD_CPU_CV 1.19
VDD_GPU_SOC 13.88
VDD_SYS5V 6.08
VDD_VDD2_1V8A0 1.82
Total_module 22.96

Thanks

Thanks for the feedback.

We are trying to reproduce this again internally.
Will share more information with you later.

Thank you AastaLLL,

I have set the clocks with with this command

sudo jetson_clocks & sudo jetson_clocks --show

SOC family:tegra234  Machine:Jetson AGX Orin
Online CPUs: 0-3
cpu0: Online=1 Governor=schedutil MinFreq=1113600 MaxFreq=1113600 CurrentFreq=1113600 IdleStates: WFI=1 c7=1 
cpu1: Online=1 Governor=schedutil MinFreq=1113600 MaxFreq=1113600 CurrentFreq=1113600 IdleStates: WFI=0 c7=0 
cpu10: Online=0 Governor=schedutil MinFreq=115200 MaxFreq=2201600 CurrentFreq=499200 IdleStates: WFI=0 c7=0 
cpu11: Online=0 Governor=schedutil MinFreq=115200 MaxFreq=2201600 CurrentFreq=499200 IdleStates: WFI=0 c7=0 
cpu2: Online=1 Governor=schedutil MinFreq=1113600 MaxFreq=1113600 CurrentFreq=1113600 IdleStates: WFI=0 c7=0 
cpu3: Online=1 Governor=schedutil MinFreq=1113600 MaxFreq=1113600 CurrentFreq=1113600 IdleStates: WFI=0 c7=0 
cpu4: Online=0 Governor=schedutil MinFreq=115200 MaxFreq=2201600 CurrentFreq=115200 IdleStates: WFI=0 c7=0 
cpu5: Online=0 Governor=schedutil MinFreq=115200 MaxFreq=2201600 CurrentFreq=115200 IdleStates: WFI=0 c7=0 
cpu6: Online=0 Governor=schedutil MinFreq=115200 MaxFreq=2201600 CurrentFreq=115200 IdleStates: WFI=0 c7=0 
cpu7: Online=0 Governor=schedutil MinFreq=115200 MaxFreq=2201600 CurrentFreq=115200 IdleStates: WFI=0 c7=0 
cpu8: Online=0 Governor=schedutil MinFreq=115200 MaxFreq=2201600 CurrentFreq=499200 IdleStates: WFI=0 c7=0 
cpu9: Online=0 Governor=schedutil MinFreq=115200 MaxFreq=2201600 CurrentFreq=499200 IdleStates: WFI=0 c7=0 
GPU MinFreq=408000000 MaxFreq=408000000 CurrentFreq=408000000
EMC MinFreq=204000000 MaxFreq=2133000000 CurrentFreq=2133000000 FreqOverride=1
DLA0_CORE MinFreq=0 MaxFreq=614400000 CurrentFreq=614400000
DLA0_FALCON MinFreq=0 MaxFreq=294400000 CurrentFreq=294400000
DLA1_CORE MinFreq=0 MaxFreq=614400000 CurrentFreq=614400000
DLA1_FALCON MinFreq=0 MaxFreq=294400000 CurrentFreq=294400000
PVA0_VPS0 MinFreq=0 MaxFreq=307200000 CurrentFreq=307200000
PVA0_AXI MinFreq=0 MaxFreq=217600000 CurrentFreq=217600000
FAN Dynamic Speed control=active hwmon1_pwm=58
NV Power Mode: MODE_15W
[1]+  Done                    sudo jetson_clocks

Here the GPU MaxFreq is 408000000 Hz,

I have monitored the frequencies, while using the “trtexec”, for the GPU model,
The GPU freq reached the 1300500000 Hz

I guess that is the reason for the increase in power consumption.

Could you please any command to restrict the GPU freq. specific to the power mode

Thanks,
Sairam

Hi,

Thanks for sharing this information with us.

It looks like the clock is not set for 15W mode somehow.
We are still checking this issue with our internal team.
Will share more information with you later.

Thanks.

Hi,

We have located the root cause.
The fix will be available in our future release.

Thanks.

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