Replies: 4 comments 12 replies
-
the main thing that is going to be limiting you is GPU, using the CPU for the decoding will be slower and in general might run in to issues with things happening in a timely manner on the system. As for what GPU, well you'd want one that has enough capacity to decode most if not all of the streams |
Beta Was this translation helpful? Give feedback.
-
you wouldn't get a discrete GPU if your goal is to reduce power and heat, especially when it's not warranted by your existing performance metrics. stick w/corals for object detection, avoid discrete gpus, get a cpu w/integrated gpu/vaapi if you're concerned in that area, reduce RAM to no more than 16GB as that consumes power too. as documentation says, use h264 wherever possible for maximum compatibility/user experience. ensure you are using low-resolution streams for detection. post your config.yml w/o passwords if you want more eyeballs on that. curious...how are you supporting 4 x mini-pci-E corals? your hardware choices will be guided by those to an extent. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
yes, depending on the detector you choose. Compreface can do it as long as cpu has avx extensions. to my knowledge there's no native facial recognition planned in frigate. if you look around you'll find that most folks use https://github.com/mincka/double-take to provide integration with face detectors like compreface via MQTT (take a snapshot from frigate, run detection, update the event if appropriate). personally i'd never install a dedicated gpu for facial recognition as i don't have anywhere near enough volume of events w/persons in my cameras to warrant it. certainly there are many worthwhile applications: any entry/exit (condominium, retail store, employee clock-in/out, etc). 27 cameras is on the larger side as far as frigate goes so that suggests facial recognition might have some value for you. ymmv
yup, I get it. i'm NVMe for production....satisfied requirements and is far cooler/quieter. I only use rotational for backups and then I just spin them up daily, do the backups, and power them off. |
Beta Was this translation helpful? Give feedback.
-
Hello. I am running Frigate 0.13.2 (will migrate to 0.14 with a planned hardware upgrade, unless you think that's a bad idea) in a rather intense application and am wondering what you would recommend for CPU, GPU, and drives. 4 x PCIe Corals will be moved to the new system; they get inference speeds of 7-8 ms normally. I have read the "Recommended Hardware" section, but I think that the circumstances warrant a query.
There are 27 cameras, mostly Dahua/EmpireTech 4k units (Dahua/EmpireTech: 8 x IPC-T58IR-ZE-S3, 6 x IPC-Color4K-T, 3 x IPC-T5842T-ZE, 2 x PTZ5A4K-25X, 2 x PTZ5A4M-25X; Amcrest: 2 x IP4M-1055EW and 1 x IP2M-850EB; Reolink 2 x Video Doorbell PoE and 1 x Video Doorbell WiFi). All cameras are being both recorded and detected.
The current system is an old custom Super Micro server in a 2 U case with 2 x 3.00 GHz Intel Xeon E5-2690 v2s (10-core CPUs), 384 GB of ECC RAM (I think that its usual use is about 15 GB), and no dedicated GPU. The system drive is a 256 GB Samsung 850 Pro MZ-7KE256BW. The storage drives are 4 x 8 TB Western Digital WD80PURZ in RAID 5. It handles the load (CPU utilization about 25% most of the time) and records without a hitch, but uses way too much (electrical) power for the application, not only to run the system, but to cool the room, haha.
So, what direction should I go in designing a new system (CPU, GPU, drives) for Frigate? Your input is appreciated and, I think, of use to others setting up Frigate servers, as well.
Beta Was this translation helpful? Give feedback.
All reactions