Guide · MemryX MX3 (M.2)
MemryX MX3 for Frigate: Total FPS, Not Inference Time
MemryX MX3 M.2 benchmarks for Frigate, and why you must use Total FPS (not 1000/ms) to size cameras.
The MemryX MX3 is a community-supported M.2 accelerator added in Frigate 0.17. It is pipelined, so the usual 1000 ÷ inference-ms rule does not apply.
MX3 sizing from Total FPS (÷ 5 fps per camera, theoretical): YOLO-NAS-S 320 → ~75 · YOLOv9s 320 → ~76 · YOLO-NAS-S 640 → ~27 · YOLOv9s 640 → ~22 · YOLOX-S 640 → ~52 · SSDlite MobileNet v2 320 → ~211.
Known issues and gotchas
- Use Total FPS: "the maximum frames per second supported ... cannot be calculated as 1/latency"; use the MX3 Total FPS column (docs).
- Docs Total FPS (Intel 13700 host): YOLO-NAS-S 320 ~378, 640 ~138; YOLOv9s 320 ~382, 640 ~110; YOLOX-S 640 ~263; SSDlite MobileNet v2 320 ~1056 (docs).
- ARM hosts may be slower: Raspberry Pi and other SBCs "may limit total FPS" (docs).
- Default model is YOLO-NAS-Small; multiple MX3 modules can be combined (docs).
Related
Live numbers for this guide's hardware
Generated from the database at build timeThe text above is written by hand and never contains numbers or prices. Everything below is pulled from builds.json and hardware.json when the site is built, so it stays current without touching the guide.
MemryX MX3 (M.2)
AcceleratorMemryX
Median total fps
320.5 fps
all models · 6 usable builds
Capacity · estimate
~110 det/s
yolov9-s · 640 median 110 fps · 1 detector
Cameras · estimate
26
5 fps · Typical · under 60% (44 before overload)
Price
not tracked yet
no retailer link listed
BuildSourceModelSpeedCamsFrigatePosted