Argus high cpu usage streaming cameras

[kes25c]

I found several other posts (linked at the bottom of this post) in these forums about the unexpectedly high CPU usage of Argus. These seem to match my measured CPU loads: ~15-20% of a core per camera @ 30fps and ~30-40% of a core per camera @ 60fps. Unfortunately, there are no answers provided as to why Argus uses so much CPU. It would be awesome if someone from Nvidia could answer these questions:

1. What is Argus doing to cause such high CPU load since the heavy computations should be offloaded to separate hardware?
2. Can Argus’ CPU usage be improved or is there a technical reason it cannot be?
3. If Argus’ CPU usage can be improved, does Nvidia plan on addressing it? If so, what’s the timeline for that?

For a single camera system the current usage might not be problematic, but it adds up very quickly for multi-camera systems. It definitely has an impact on how we proceed algorithm wise.

Nvargus-daemon CPU Load difference between GStreamer (nvarguscamerasrc) and application using LibArgus

We are currently transitioning a multi-camera streaming application from a GStreamer solution (using nvarguscamerasrc) to one that uses LibArgus directly. While using LibArgus directly, we noticed that the CPU load of the nvargus-daemon process has increased by about 6-8% (of a CPU core), even though the input cameras and framerates haven’t changed. When looking at the threads spun up by the nvargus-daemon, it seems like the majority of the CPU difference can be attributed to some unnamed threa…

Working with ISP without libargus

Hello! Can you please provide me with some (if any) ways (documentation, tutorials, examples) of working with ISP without libargus library? Thank you in advance, Roman Abakumov

Performance of nvargus-daemon

Hello, we are using the TX2 with R32.2.1 on a customer carrier board. The main application is to capture images from up to 6 image sensors (IMX290 1920x1080 30fps) connectd via CSI using the nvargus-daemon by the Multimedia API. As we are now in the phase of optimizing the system it turned out that the nvargus-daemon consumes a lot of system performance. As the camera images need to be further processed by OpenCV after ‘acquireFrame’ the yuv420 image is getting color converted (ARGB32) and li…

question about argus_camera

I run 3 argus_camera apps to check the video from AR0144 on TX2 board. I find an issue, 3 argus_camera and 1 nvargus-daemon will consume almost 1 CPU core. In my opinion, it is too high. I want to know it is reasonable or not? If it is reasonable, could you explain a bit on it? [20191021201811.jpg] [20191021201811.jpg]

Expected load for single camera with gst nvarguscamera around 20%?

I am currently seeing between 20% and 30% load on the whole system, as soon as I start reading from the camera using gstreamer. I just wanted to confirm, that this is as expected (I personally had expected much less load). My setup: Jetson TX2 Jetpack 4.2 (installed via SDK Manager) CSI-2 MIPI IMX185 from Leopard imaging I ran different types of pipelines, for example: This results in around 15% load on all 4 CPUs as well as the GPU: gst-launch-1.0 nvarguscamerasrc ! 'video/x-raw(memory:N…

Gstreamer input nvcamerasrc vs v4l2src

I’ve managed to get input from a TC358743 chip into Gstreamer using v4l2src, however this is not using the NVMM to pass data over to the encoder, as such I believe this is why my H265 pipeline is so choppy (although I might be wrong). Should I be piping the output into the tegra-camera-platform and using nvcamerasrc instead? How does it differ to v4l2src, is there one?