High CPU Usage (Hardware Acceleration)

[mirisbowring]

Hi,

first of all, i want to thank for the great work to enable rtsp support for reolink bundle cams.

I am running 8 RLC-410 cams and they are working fine.
Unfortunately, my Server Idle usage (i5 7500 32GB Ram) went from 10% to 60-80% after enabling the surveillance system, which causes many stability problems for the other programs on my server.
First, i thought this is a frigate thing, but it appears that the cpu usage comes from neolink.

Therefor my question is:
Is this expected? Is there any option to reduce the cpu usage? What part of neolink is causing this usage?

Thanks!

[QuantumEntangledAndy]

Are you using the last stable release or the alpha stuff on the mqtt_push branch? There are a few optimisations on the cpu that have yet to land in the master that help with cpu.

[QuantumEntangledAndy]

Gstreamer is used for all the stream data. There are a couple of hardware gstreamer decoder/encoders in their cuda packages but havent really looked at it

[QuantumEntangledAndy]

Not sure I really want to go through this route without first trying other things. Would also need to make all of these changes optional in some way so its a lot of work

[mirisbowring]

HW accel is supported on most cpu (AMD/Intel) snd would completely offload the whole processing which would reduce the cpu to like 2% for neolink.

[mirisbowring]

@QuantumEntangledAndy
I did some minor investigation (I had no experience with RUST in the past).
As far as i have seen, we would only need to install "gstreamer1.0-vaapi" in the Dockerfile.

Then, here: https://github.com/QuantumEntangledAndy/neolink/blob/4a94a2ddb29bed207307eb2de744748190e8577f/src/common/streamthread.rs#L469C74-L469C85
We would need to check whether vaapi is available - can be done via vainfo (especially the vaapih264dec: VA-API H264 decoder, vaapih264enc: VA-API H264 encoder, vaapih265dec: VA-API H265 decoder or vaapih265enc: VA-API H265 encoder). If so, we would start the line with camera.start_video_vaapi(...) instead of camera.start_video(...)

In theory you could skip the vainfo verification process and let the user decide whether to use this or not by setting "VAAPI" in the config file and therefor the user would have to check whether his cpu allows VAAPI and could enable it if he wants to.

[idle-user]

Hardware acceleration would be very nice to have.

I also have no experience in rust but I will attempt what you suggested when I have some time. If I make any results I'll throw in a pull request.

Also wanted to look into the memory leak issue. At the moment, I just have a cron restarting the container every 2-3 hrs.