Most arenвЂ™t using much or any CPU and seem to be tied to different parts of the image pipeline - DeFogStage, GpuBlitStage, SharpenStage, VideoStabilization, HdfxStage, AoltmStage, etcвЂ¦ IвЂ™m really curious now exactly what the SCF_Execution and CaptureSchedule threads are doing to eat up so much CPU. An additional ~15 are created per streamed camera. From what I can tell, simply initializing Argus creates 25 threads. The total CPU usage by argus (mainly in SCF_Execution and CaptureSchedule) scales mostly linearly as a function of total number of images per second ( #_cameras * FPS).Д®DIT 3: Argus creates a somewhat insane number of threads. There are always 12 SCF_Execution threads regardless of number of cameras. Is there anything else we could do to reduce the cpu load?Д®DIT: if it matters, IвЂ™m using CAPTURE_INTENT_PREVIEW in createRequest and leaving everything else (edge enhancement mode, denoise mode, etcвЂ¦) at defaults.Д®DIT 2: after more testing it looks like the number of SCF_Execution threads isnвЂ™t dependent on the number of cameras being streamed. We can reduce the cpu usage by ~33% by running the cameras at 10fps instead of 30fps, but it isnвЂ™t a great solution. Total time for SCF_Execution and CaptureSchedule seems to scale linearly with the fps. The rest is in the Configure, CreateSession, FreeSession so a lot of time seems to just be overhead. In the profiling results the cpu usage of copyToNvBuffer seems to break down into VicConfigure, VicCreateSession, VicExecute, VicFreeSession. That also takes a good bit of cpu time (~2.5% for each camera) even though it uses the VIC. No useful symbols, but most of the time is again in libnvos.so and libnvscf.so.ДЄfter acquireFrame we are getting the IImageNativeBuffer and calling copyToNvBuffer to scale the image and save it into another nvbuffer. Is it possible some of this is image processing? or does that all happen on the ISP?Д¬aptureSchedule. I donвЂ™t have symbols to know what most of the other processing is doing, but itвЂ™s mostly all in libnvscf.so and libnvos.so.

According to the profiling something like ~10% of SCF_Execution is just powf() calls. Looks like there are two SCF_Execution threads per camera (I see 12 of those threads). Currently we are using JetPack 4.2.2 with argus in single process mode.Д«ased on profiling results, the biggest parts appear to be: So itвЂ™s taking more than a core just to stream the cameras without any other processing.

WeвЂ™ve noticed that just streaming the cameras by calling iFrameConsumer->acquireFrame() incurs a pretty high cpu load (~110% according to top).

We have six csi cameras that we get images from using argus 30fps.

Argus developer 7