reasonable-panel3162

ok understood the reason! sometimes a stupid mistake can ruin everything. I just don't know when /media/frigate became /frigate/media in my configuration, I think the moment I created that shared for videos I made that mistake. Basically Frigate was saving the videos inside the docker, now all things are good.

Ok, after I added this again, here are the results after two days: Filesystem Size Used Avail Use% Mounted on /dev/loop2 108G 40G 66G 38% / tmpfs 68M 0 68M 0% /dev shfs 2.0T 526G 1.5T 27% /frigate/media shm 68M 3.2M 64M 5% /dev/shm /dev/loop2 108G 40G 66G 38% /etc/hosts tmpfs 1.1G 1.6M 999M 1% /tmp/cache overlay 17G 1.3G 16G 8% /usr/bin/nvidia-smi rootfs 17G 1.3G 16G 8% /etc/vulkan/icd.d/nvidia_icd.json tmpfs 17G 13k 17G 1% /proc/driver/nvidia tmpfs 17G 4.1k 17G 1% /etc/nvidia/nvidia-application-profiles-rc.d overlay 17G 1.3G 16G 8% /lib/firmware/nvidia/545.29.02/gsp_ga10x.bin devtmpfs 8.4M 0 8.4M 0% /dev/nvidia0 I just don't know why /dev/loop2 is consuming a lot, you can see I have tmp/cache for 1GB Any idea what's wrong there?

You are totally correct, idk why this has been removed. I just add it again now

Frigate-nvr is consuming lots of docker-image, at the moment around 80GB. I ran df -H inside frigate container and this is the result: Filesystem Size Used Avail Use% Mounted on /dev/loop2 108G 83G 23G 79% / tmpfs 68M 0 68M 0% /dev shfs 2.0T 520G 1.5T 26% /frigate/media shm 68M 5.0M 63M 8% /dev/shm /dev/loop2 108G 83G 23G 79% /etc/hosts overlay 17G 1.3G 16G 8% /usr/bin/nvidia-smi rootfs 17G 1.3G 16G 8% /etc/vulkan/icd.d/nvidia_icd.json tmpfs 17G 13k 17G 1% /proc/driver/nvidia tmpfs 17G 4.1k 17G 1% /etc/nvidia/nvidia-application-profiles-rc.d overlay 17G 1.3G 16G 8% /lib/firmware/nvidia/545.29.02/gsp_ga10x.bin devtmpfs 8.4M 0 8.4M 0% /dev/nvidia0 Update 1: * To fix the issue at the moment, I recreated the image. * When I created it it was 8-9GB and now it's 13GB

I'm such an idiot, later I checked that frigate is using NVIDIA GPU and as a mistake I only run it inside the docker, I thought I also did outside of docker. Thanks and sorry.

Both

I can't also get my head over it why it's not working, there is nothing in nvidia-smi but from the CPU usage I can guess it's using GPU. If I disable hardware acceleration the CPU usage for a single camera goes above 5 percent, with that enabled it remains below 2%. it works better than fine with jellyfin for example, it transcode like hot sword on butter. Thanks for the help.

Hi, thanks for the reply. I'll remove gpus=all I already ran the ffmpeg -decoders and here is the result, it supports: libavutil 57. 28.100 / 57. 28.100 libavcodec 59. 37.100 / 59. 37.100 libavformat 59. 27.100 / 59. 27.100 libavdevice 59. 7.100 / 59. 7.100 libavfilter 8. 44.100 / 8. 44.100 libswscale 6. 7.100 / 6. 7.100 libswresample 4. 7.100 / 4. 7.100 libpostproc 56. 6.100 / 56. 6.100 V..... av1_cuvid Nvidia CUVID AV1 decoder (codec av1) V..... h264_cuvid Nvidia CUVID H264 decoder (codec h264) V..... hevc_cuvid Nvidia CUVID HEVC decoder (codec hevc) V..... mjpeg_cuvid Nvidia CUVID MJPEG decoder (codec mjpeg) V..... mpeg1_cuvid Nvidia CUVID MPEG1VIDEO decoder (codec mpeg1video) V..... mpeg2_cuvid Nvidia CUVID MPEG2VIDEO decoder (codec mpeg2video) V..... mpeg4_cuvid Nvidia CUVID MPEG4 decoder (codec mpeg4) V..... vc1_cuvid Nvidia CUVID VC1 decoder (codec vc1) V..... vp8_cuvid Nvidia CUVID VP8 decoder (codec vp8) V..... vp9_cuvid Nvidia CUVID VP9 decoder (codec vp9)

Hi everyone, I'm totally new to Unraid and after spending 4 hours, I got almost things ready. I have a weird problem with Frigate and Nvidia at the moment. Frigate can see my GPU, but it won't use it for transcoding, both inside the container and in the host if I run nvidia-smi I can see it gives me the info of my GPU but there are no process are using it. In the frigate configuration, I have this: ffmpeg: hwaccel_args: preset-nvidia-h264 and to run my container with Nvidia GPU, I've added --runtime-nvidia and --gpus=all + two variables for gpu-id and capabilities. For a second I was happy it found my GPU but it's not using it --- Update 1 --- What's weird for me, when I remove the hwaccel_args the cpu usage goes up like 5-6 for a single camera, but when bring back the hwaccel_args the cpu usage goes down to fixed 2%