Can I offload object detection to another server? #19220
Replies: 2 comments 1 reply
-
|
Based on the available sources, Frigate does not support offloading object detection to remote servers or other Frigate instances (1)(2)(3)(4). The detectors are designed to run locally within the same Frigate instance. Regarding your specific concerns: Multiple Detectors: When using multiple detectors, they run in dedicated processes but pull from a common queue of detection requests from across all cameras (3)(4). This means adding more CPU detectors will spread the load across processes rather than offload to different machines. CPU Detector Performance: The CPU detector is not recommended for general use (1)(3). If you don't have GPU or Edge TPU hardware, using the OpenVINO Detector in CPU mode is often more efficient than using the CPU detector (1)(3). Coral TPU Fallback: There's a GitHub issue discussing fallback functionality when a Coral is unplugged, but this appears to be a duplicate of an existing request and doesn't indicate current support for automatic fallback (5). Alternative Solutions:
detectors:
ov:
type: openvino
device: CPUThe recommended approach would be to configure OpenVINO on your main system rather than trying to distribute detection across multiple servers. 📚 Sources: |
Beta Was this translation helpful? Give feedback.
-
|
Bump |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm currently using frigate with the default CPU detector. Unfortunately frigate is running on an older Xeon E5-2630L and this uses a lot of the cpu.
I also have three other machines with dual E5-2660 v2 cpus in them. Is it possible to offload the object detection from the main frigate instance to another frigate instance on one or more of these other servers?
Note: I do have a usb coral tpu, but for some reason it keeps disappearing from the machine and I have to unplug/replug it in for it to be detected again which causes frigate to be broken until then. This also goes through proxmox -> docker layers. I'd be happy if frigate would just use the cpu as a fallback until something better is available too, but configuring multiple detectors seems to only spread the load instead.
Beta Was this translation helpful? Give feedback.
All reactions