Temporary High GPU / iowait on 0.15.0-rc1

[FeatherKing]

Hi all, ive been looking forward to the rc for a while. had no issues with the upgrade. Saw some weird GPU behavior that eventually stopped but my system had abnormal iowait while it was happening. I was about to restart the container but then it went to normal. During the upgrade it did ask me to double my SHM which i did. I am using an integrated intel gpu. there is vaapi for my reolink doorbell and everything else is qsv. This setup has been fine on 0.14.1 for a while. I have not enabled the new explore tab yet. i wanted to get a baseline for performance before adding new features. the blue dashed vertical line is when i upgraded from 0.14.1 to 0.15.0-rc1.

i did restart go2rtc at 10:52:04 log time. That didnt immediately fix things so i was about to restart but then everything went back to normal. I am seeing a lot of go2rtc WRN events that i didnt have before. They are my wifi cameras and things seem to be working fine despite the WRN events.

frigate_20250125_1057.log
config.txt

[NickM-27]

You can run intel_gpu_top and see what is using high gpu. In general though it's likely the usage of vaapi with ffmpeg 7.0 on this newer Intel hardware.

there is vaapi for my reolink doorbell

You should use qsv for this now, there have been fixes put in place

[FeatherKing]

great. i just switched it to qsv and ill monitor.

[FeatherKing]

fyi, go2rtc still had a bunch of processes using vaapi. I had configuration like

hagdrivewaycam:

• rtsp://wyze.replace.me:8554/hag-driveway
• ffmpeg:hagdrivewaycam#video=h264#hardware#audio=aac

in the go2rtc docs on hardware acceleration. it mentions that

PS. Supported via VAAPI engine on Linux and DXVA2+QSV engine on Windows.

i tried to force qsv with the below config and i can confirm that all vaapi ffmpeg processes are gone now. Not sure if that is worth mentioning in the frigate docs somewhere

hagdrivewaycam:

• rtsp://wyze.replace.me:8554/hag-driveway
• ffmpeg:hagdrivewaycam#video=h264#hardware=qsv#audio=aac

[FeatherKing]

nevermind, it seems to be falling back to cpu. ill put it back how it was for now and watch it some more