[HW Accel Support]: NUC5i5RYH #14949

USER19464727 · 2024-11-13T02:54:40Z

USER19464727
Nov 13, 2024

Describe the problem you are having

Based on performance metrics and sometimes crashing, I think my GPU isn't doing much (see screenshot of CPU at 34% and GPU at 0%). I'm running HAOS on an Intel NUC5i5RYH. I have the following in my frigate.yaml file

ffmpeg:
  hwaccel_args: preset-vaapi

I have also tried the following in the Frigate Full-Access add-on (with protection mode disabled): LIBVA_DRIVER_NAME=i965 (I'm guessing that's where to put it?) I'm a bit over my head with this stuff and could use some guidance.

Version

0.14.1-f4f3cfa

Frigate config file

detectors:
  coral:
    type: edgetpu
    device: usb

ffmpeg:
  hwaccel_args: preset-vaapi

go2rtc:
  streams:
    doorbell_main:
      - rtsp://user:[email protected]:554/Preview_01_main#backchannel=0
      - rtsp://user:[email protected]:554/Preview_01_sub
      - ffmpeg:doorbell_main#audio=opus#hardware
    doorbell_sub:
      - rtsp://user:[email protected]:554/Preview_01_sub
      - ffmpeg:doorbell_sub#audio=opus#hardware

cameras:
  doorbell:
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/doorbell_main
          input_args: preset-rtsp-restream-low-latency
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/doorbell_sub
          input_args: preset-rtsp-restream-low-latency
          roles:
            - detect
            - audio

docker-compose file or Docker CLI command

N/A

Relevant Frigate log output

2024-11-13 02:37:38.048235391  [INFO] Preparing Frigate...
2024-11-13 02:37:38.118338443  [INFO] Starting Frigate...
2024-11-13 02:37:41.491900599  [2024-11-12 21:37:41] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2024-11-13 02:37:41.497088886  [2024-11-12 21:37:41] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-11-13 02:37:41.501981983  [2024-11-12 21:37:41] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-11-13 02:37:41.612164537  [2024-11-12 21:37:41] frigate.util.config            INFO    : frigate config does not need migration...
2024-11-13 02:37:48.478376042  [rtsp @ 0x1d716500] method DESCRIBE failed: 404 Not Found
2024-11-13 02:37:58.489690876  [2024-11-12 21:37:58] peewee_migrate.logs            INFO    : Starting migrations
2024-11-13 02:37:58.491367414  [2024-11-12 21:37:58] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-11-13 02:37:59.930161466  [2024-11-12 21:37:59] frigate.app                    INFO    : Recording process started: 395
2024-11-13 02:37:59.937310380  [2024-11-12 21:37:59] frigate.app                    INFO    : Recording process started: 397
2024-11-13 02:37:59.942400947  [2024-11-12 21:37:59] frigate.app                    INFO    : go2rtc process pid: 98
2024-11-13 02:37:59.981134529  [2024-11-12 21:37:59] detector.coral                 INFO    : Starting detection process: 424
2024-11-13 02:37:59.988519322  [2024-11-12 21:37:59] frigate.app                    INFO    : Output process started: 426
2024-11-13 02:37:59.997429903  [2024-11-12 21:37:59] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2024-11-13 02:38:00.024537773  [2024-11-12 21:38:00] frigate.comms.dispatcher       INFO    : Turning off recordings for CAM11
2024-11-13 02:38:00.024543307  [2024-11-12 21:38:00] frigate.comms.dispatcher       INFO    : Turning off snapshots for CAM11
2024-11-13 02:38:00.024549939  [2024-11-12 21:38:00] frigate.comms.dispatcher       INFO    : Turning off audio detection for CAM11
2024-11-13 02:38:00.025529837  [2024-11-12 21:38:00] frigate.comms.dispatcher       INFO    : Turning off detection for CAM11
2024-11-13 02:38:00.027005114  [2024-11-12 21:38:00] frigate.comms.dispatcher       INFO    : Turning off motion for CAM11
2024-11-13 02:38:00.526901060  [2024-11-12 21:38:00] frigate.app                    INFO    : Camera processor started for doorbell: 444
2024-11-13 02:38:00.527078306  [2024-11-12 21:38:00] frigate.app                    INFO    : Camera processor not started for disabled camera CAM1
2024-11-13 02:38:00.533761757  [2024-11-12 21:38:00] frigate.app                    INFO    : Camera processor started for CAM2: 445
2024-11-13 02:38:00.542699517  [2024-11-12 21:38:00] frigate.app                    INFO    : Camera processor started for CAM11: 453
2024-11-13 02:38:00.557097118  [2024-11-12 21:38:00] frigate.app                    INFO    : Camera processor started for CAM12: 461
2024-11-13 02:38:00.558204286  [2024-11-12 21:38:00] frigate.app                    INFO    : Capture process started for doorbell: 469
2024-11-13 02:38:00.564951124  [2024-11-12 21:38:00] frigate.app                    INFO    : Capture process not started for disabled camera CAM1
2024-11-13 02:38:00.566318382  [2024-11-12 21:38:00] frigate.app                    INFO    : Capture process started for CAM2: 479
2024-11-13 02:38:00.582711659  [2024-11-12 21:38:00] frigate.app                    INFO    : Capture process started for CAM11: 483
2024-11-13 02:38:00.585844794  [2024-11-12 21:38:00] frigate.app                    INFO    : Capture process started for CAM12: 487
2024-11-13 02:38:00.597465536  [2024-11-12 21:38:00] frigate.app                    INFO    : Audio process started: 491
2024-11-13 02:38:02.622146304  [2024-11-12 21:38:02] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found

Relevant go2rtc log output

2024-11-13 02:37:38.086682509  [INFO] Preparing new go2rtc config...
2024-11-13 02:37:38.155645514  [INFO] Got IP address from supervisor: 192.168.50.15
2024-11-13 02:37:38.216095905  [INFO] Got WebRTC port from supervisor: 8555
2024-11-13 02:37:39.219732161  [INFO] Starting go2rtc...
2024-11-13 02:37:39.387349420  21:37:39.387 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-11-13 02:37:39.387376886  21:37:39.387 INF config path=/dev/shm/go2rtc.yaml
2024-11-13 02:37:39.388200543  21:37:39.388 INF [api] listen addr=:1984
2024-11-13 02:37:39.388393549  21:37:39.388 INF [rtsp] listen addr=:8554
2024-11-13 02:37:39.388661454  21:37:39.388 INF [webrtc] listen addr=:8555/tcp
2024-11-13 02:37:48.052097415  [INFO] Starting go2rtc healthcheck service...
2024-11-13 02:37:48.478056141  21:37:48.477 WRN [rtsp] error="streams: dial tcp 192.168.50.211:554: i/o timeout" stream=CAM1_sub

FFprobe output from your camera

i don't think I can run this

Install method

HassOS Addon

Object Detector

Coral

Network connection

Wired

Camera make and model

Amcrest IP8M-2779EW and Reolink Doorbell

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Saw this in the hardware info:


{"return_code":0,"stderr":"","stdout":"vainfo:VA-APIversion:1.17(libva2.10.0)nvainfo:Driverversion:InteliHDdriverforIntel(R)GenGraphics-23.1.1()nvainfo:SupportedprofileandentrypointsnVAProfileNone:tVAEntrypointVideoProcnVAProfileNone:tVAEntrypointStatsnVAProfileMPEG2Simple:tVAEntrypointVLDnVAProfileMPEG2Simple:tVAEntrypointEncSlicenVAProfileMPEG2Main:tVAEntrypointVLDnVAProfileMPEG2Main:tVAEntrypointEncSlicenVAProfileH264Main:tVAEntrypointVLDnVAProfileH264Main:tVAEntrypointEncSlicenVAProfileH264Main:tVAEntrypointFEInVAProfileH264High:tVAEntrypointVLDnVAProfileH264High:tVAEntrypointEncSlicenVAProfileH264High:tVAEntrypointFEInVAProfileVC1Simple:tVAEntrypointVLDnVAProfileVC1Main:tVAEntrypointVLDnVAProfileVC1Advanced:tVAEntrypointVLDnVAProfileJPEGBaseline:tVAEntrypointVLDnVAProfileH264ConstrainedBaseline:tVAEntrypointVLDnVAProfileH264ConstrainedBaseline:tVAEntrypointEncSlicenVAProfileH264ConstrainedBaseline:tVAEntrypointFEInVAProfileVP8Version0_3:tVAEntrypointVLD"}

Answered by NickM-27

Nov 19, 2024

yeah it does seem like there is not much headroom in the current hardware

View full answer

NickM-27 · 2024-11-14T13:40:41Z

NickM-27
Nov 14, 2024
Collaborator Sponsor

your biggest user of CPU is go2rtc, you can reduce CPU usage by changing your config to:

    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/doorbell_main
          input_args: preset-rtsp-restream-low-latency
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/doorbell_sub
          input_args: preset-rtsp-restream-low-latency
          roles:
            - detect
        - path: rtsp://127.0.0.1:8554/doorbell_sub?audio
          input_args: preset-rtsp-restream-low-latency
          roles:
            - audio

5 replies

USER19464727 Nov 14, 2024
Author

I appreciate your input. That did not seem to change the CPU usage. A few questions:

Is it normal for the GPU % to be consistently under 1%? The more I look into it I think it's recognized (due to info in "Hardware Info" and the fact that it has any % listed, it just seems like it's not doing much)
Is it normal for each camera to take up about 8% of CPU? I tried removing cameras one by one and each time it dropped CPU by about 8%. That plus the individual usage indicates there's not one culprit.
I wanted to run 8 Amcrest 4K cameras and 1 Reolink doorbell camera plus 2 Amcrest ASH41 cameras on this Intel NUC 5i5RYH. The 2 ASH41 cameras are CAM11 and CAM12 and I only have one 4K cameras hooked up right now. Based on it already sometimes locking up, I'm worried it's not up to the task unless I can make some changes to settings. I also have an HP Thin Client t730, but I can't seem to get any GPU recognized on that with Frigate, so it's no better off than my NUC.

NickM-27 Nov 14, 2024
Collaborator Sponsor

yes, GPU does not have to work very hard to decode a sub stream
depends on the CPU, for an i5 that is not that high
can you define locking up?

USER19464727 Nov 14, 2024
Author

Sometimes I go to look at the cameras and I click on Frigate in the sidebar and suddenly it becomes unresponsive. I am able to click on other things and a short while later the Frigate add-on has restarted. I cannot recall what the log files said when this happens. It may or may not be related, but it did make me check the CPU usage and if it's around 30% idle, I could see it going well above 60% (I have briefly seen it above 60%) if the cameras are simultaneously detecting things. This is without me adding the remaining cameras. I can revisit frame rates, resolutions, etc, but I'm wondering if, based on having experience with other systems, if it is best for me to invest in a better computer.

NickM-27 Nov 19, 2024
Collaborator Sponsor

yeah it does seem like there is not much headroom in the current hardware

Answer selected by USER19464727

USER19464727 Dec 10, 2024
Author

As a follow-up for anyone looking at this. My former CPU was a Intel Core i5-5250U and I just bought a new mini PC with an Intel Core i7-12650H. According to benchmark test results at cpubenchmark.net, the new one should be about 11x better than the old. Now that I'm running Frigate (this time in a docker container instead of HAOS add-on), the CPU hovers between 3% and 4% on average with (8) 8MP cameras, a doorbell camera, and (2) 4MP cameras (using substreams for detection and full resolution for record). Performance is significantly better. The documentation and other posts I read didn't give me a good idea of CPU requirements, which generally stated that CPU usage wasn't significant if using a Coral. Of course, it's all relative and hopefully this will help others anticipate CPU usage in their situation.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

[HW Accel Support]: NUC5i5RYH #14949

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment 5 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

[HW Accel Support]: NUC5i5RYH #14949

Uh oh!

Uh oh!

USER19464727 Nov 13, 2024

Describe the problem you are having

Version

Frigate config file

docker-compose file or Docker CLI command

Relevant Frigate log output

Relevant go2rtc log output

FFprobe output from your camera

Install method

Object Detector

Network connection

Camera make and model

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Replies: 1 comment · 5 replies

Uh oh!

NickM-27 Nov 14, 2024 Collaborator Sponsor

Uh oh!

USER19464727 Nov 14, 2024 Author

Uh oh!

NickM-27 Nov 14, 2024 Collaborator Sponsor

Uh oh!

USER19464727 Nov 14, 2024 Author

Uh oh!

NickM-27 Nov 19, 2024 Collaborator Sponsor

Uh oh!

USER19464727 Dec 10, 2024 Author

USER19464727
Nov 13, 2024

Replies: 1 comment 5 replies

NickM-27
Nov 14, 2024
Collaborator Sponsor

USER19464727 Nov 14, 2024
Author

NickM-27 Nov 14, 2024
Collaborator Sponsor

USER19464727 Nov 14, 2024
Author

NickM-27 Nov 19, 2024
Collaborator Sponsor

USER19464727 Dec 10, 2024
Author