You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two same model cameras (Wyze Cam v3, being broadcast through docker-wyze-bridge)- one was setup with detection and a low-res substream (for detection purposes), while the other is setup without detection (just recording). Both cameras are outputting the same resolution. I noticed the one without detection had significantly higher average CPU usage 50%+ while the other was consistently below 10%. This feels weird to be expected behavior because if I enable detection and setup the low-res substream on the other camera, its CPU usage drops to that of the other camera.
Even when detect is disabled the stream is still decoded, if you don't provide a sub stream then the main stream will be decoded which will increase CPU usage.
@NickM-27 Is this expected behavior or a known issue? Why does Frigate need to decode the stream if I’m not using it for detection purposes? If it’s expected then perhaps we add a note to the docs that states the stream will be decoded regardless and this can significantly impact CPU usage?
motion detection
a. for recordings
b. for the motion detector in HA integration
c. for birdseye in motion mode
the latest.jpg and other various APIs / live view
for birdseye in general
There is a feature request to make this not always be the case but as outlined above many things depend on this decoded stream so it will be complicated to implement.
The docs can be updated
NickM-27
changed the title
[Support]: FFmpeg CPU usage significantly higher without low-res substream even though detect is disabled
[Support]: ffmpeg still decoding stream with detection disabled
Nov 6, 2023
Describe the problem you are having
I have two same model cameras (Wyze Cam v3, being broadcast through docker-wyze-bridge)- one was setup with detection and a low-res substream (for detection purposes), while the other is setup without detection (just recording). Both cameras are outputting the same resolution. I noticed the one without detection had significantly higher average CPU usage 50%+ while the other was consistently below 10%. This feels weird to be expected behavior because if I enable detection and setup the low-res substream on the other camera, its CPU usage drops to that of the other camera.
Version
0.12.1-367D724
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Debian
Install method
Docker Compose
Coral version
USB
Network connection
Wired
Camera make and model
Wyze Cam V3 via docker wyze bridge
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: