How to deal high-cpu-load when useing gstreamer to encoder h264

I find that CPU-load can be very high when used gstreamer encodeing,it will slow Increased to 2.0 when encode h.264,but the cpu-occupy is no high(i am run in nvidia-jetson-nx platform with 15w-6core mode);I want to know what to do can make the CPU-load drop?I have multiple processes,high cpu-load will affecting process calls
image

gst-launch-1.0 nvarguscamerasrc !
‘video/x-raw(memory:NVMM),width=4032,height=3040,
format=(string)NV12’ !
omxh264enc control-rate=2 EnableStringentBitrate=true ! qtmux ! filesink location=test.mp4 -e

Hi,
Please run sudo tegrastats and share the prints for reference. Please also share your release version( $ head -1 /etc/nv_tegra_release ) and which camera sensors you use.


My camera sensor is SONY:IMX-477 (use 4032*3040 resolution)
The following picture is the cpu status when i run two encoder-process without any other business
image
and the terrastats log :

Could you please help me to see if there is anything wrong with it

Hi,
Thanks for sharing tegrastats. Is it single IMX477 or multiple IMX477s?

Please also running the commands and share tegrastats:

$ sudo nvpmodel -m 2
$ sudo jetson_clocks
$ gst-launch-1.0 nvarguscamerasrc ! 'video/x-raw(memory:NVMM),width=4032,height=3040,format=(string)NV12' ! fakesink

I had run the command as you suggested,and the cpu-load was Increased from 0.2 to 2.38 In three minutes;So it doesn’t have anything to do with encoder-264, does it have something to do with capture?I use single imx477 for test,I also tested with two sensors yesterday and the CPU-load was doubled.
How can I solve this problem?
image

Hi,
We have same result as yours and now it has to take the CPU usage in Argus software stacks. We will check and try to make enhancement in future release(s).

Thank you very much for your support。Can you estimate how long it will take to fix this problem?We have an important project coming online now。

This is explained in
High CPU usage streaming from CSI2 cameras on Jetson NX - #19 by JerryChang

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