System Build Advice #21619
Replies: 2 comments 2 replies
-
|
Your build looks solid for a 40-camera Frigate installation. Here are some observations based on the planning documentation: What looks good:
Considerations: GPU Concurrent Stream Limit: For commercial installations, it's important to verify the number of supported concurrent streams on your GPU - many consumer GPUs max out at around 20 concurrent camera streams(1). With 40 cameras, you may hit this limitation. Check the RTX 5060 Ti specifications for its decode session limit. CPU with NPU: The Intel Core Ultra 5 245K includes an NPU which can provide more efficient detection starting in Frigate 0.17+, though NPUs have seen limited success in community deployments and remain officially unsupported(2) Detector Configuration: You'll likely want to configure multiple detector instances to handle 40 cameras efficiently(3) Storage Calculator: Use an IP camera storage calculator like IPConfigure Storage Calculator to ensure your NAS has adequate capacity(1) Network: The 2.5Gb/s network adapter is good - make sure your NAS connection supports this speed for the recording bandwidth(1) Overall, this is a capable build, but verify the GPU's concurrent decode session limit for your camera count. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
IMHO, it might overkill. Core Ultra 5 is pretty potent all on it's own, especially the series 2 with it's updated ARC iGPU (50 concurrent streams) and NPU. You may not need a dedicated GPU at all. I would also be pretty surprised if you used up all 64GB of ram, especially with mostly 1080p cameras. It never hurts to overprovision, but given the obscene cost of DDR5 ram right now, I'd start with 32GB. You can always add a dedicated GPU and more RAM later if warranted. I think it's fine to back up to NAS, but I'd be concerned with UI performance if clips, recordings, and snapshots are all directly stored on network storage, even with a 2.5gb LAN. There is always greater latency associated associated with network storage vs local nvme storage. You also have to consider intent. Continous recording will obviously eat a ton of space, and may not be practical for local storage on say, a mini pc. Recording only detections and a few days worth of motion doesn't take up that much space and should easily fit on a 2 or 4TB nvme drive. 1080p also takes up much less space than 4K, and if your cameras support x265, space requirements will be even less. As always, YMMV. Good luck! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Just stating to put together a dedicated frigate build to handle 40 cameras at mostly 1080p, maybe 2-5 cameras being a bit higher rez. Wondering if I'm over looking anything or going a bit over kill.... the video storage will be on a dedicated NAS.
CPU
Intel Core Ultra 5 245K 4.2 GHz 14-Core Processor
CPU Cooler
be quiet! Pure Rock Pro 3 LX 61.8 CFM CPU Cooler
Motherboard
Asus TUF GAMING B860-PLUS WIFI ATX LGA1851 Motherboard
Memory
Crucial Pro 64 GB (2 x 32 GB) DDR5-5600 CL46 Memory
Storage
TEAMGROUP T-FORCE G50 512 GB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
Video Card
Asus PRIME GeForce RTX 5060 Ti 16 GB Video Card
Case
Montech X3 Mesh ATX Mid Tower Case
Power Supply
Thermaltake Smart BM3 850 W 80+ Bronze Certified Semi-modular ATX Power Supply
Wired Network Adapter
TP-Link TX201 2.5 Gb/s Ethernet PCIe x1 Network Adapter
Beta Was this translation helpful? Give feedback.
All reactions