Optimize Frigate YAML & go2rtc

I’m running Frigate on an MS-01 (13th-gen i9, USB Coral) with eight cameras—six EmpireTechs, one Amcrest, and one SV3C. Each camera provides two streams and everything is routed through go2rtc.

Right now the yaml feels bloated and I’m not convinced go2rtc is wired up the right way: CPU usage is far higher than expected, so I suspect an inefficient configuration rather than hardware limits. I need your help to audit, clean up, and fully rewrite the Frigate and go2rtc settings so the system runs smoothly.

Scope of work
• Review my current frigate.yml and go2rtc.yaml (I’ll share both as soon as we start).
• Identify and remove any redundant or conflicting directives.
• Make sure all eight cameras connect reliably on both streams.
• Tune detection, recording, and snapshot settings for the USB Coral accelerator.
• Optimise go2rtc mappings so transcoding is avoided whenever possible.
• Deliver a clear, commented yaml set that I can drop straight into my existing Docker stack.

Acceptance criteria
• CPU usage at idle ≤ 15 % and under motion load ≤ 35 %.
• No dropped frames or disconnects across any camera for a 24-hour test window.
• All edits documented inside the yaml files so I can learn from the changes.

If you’ve tamed Frigate and go2rtc before, I’d love to see your approach. Let’s get this config running as efficiently as the hardware deserves.