HomeBenchmarksHailo-8L › MobileNet Ssd Mobilenet V1
Benchmark Explorer · MobileNet Ssd Mobilenet V1 on Hailo-8L

MobileNet Ssd Mobilenet V1 on Hailo-8L: 1 row.

Method v1.0 · dataset 2026-09-07 · verified 2026-09-07 · last updated September 2026

mobilenetssd-mobilenet-v1 on Hailo-8L: 1 row (0 measured, 1 derived). Expected: INT8 1200 fps. Fastest: Hailo-8L 1200 fps (class D), Google Coral Edge TPU 153.8 fps (class C).

Change hardware, precision, runtime or add a comparison set on the live engine.

Expected range per precision

Min / median / max of the matching rows, all classes. When a precision has no row, the estimator's benchmark hierarchy (B → C → D) supplies a fallback with its tier chain reported.

PrecisionMetricNMinMedianMaxBest classMeasured
INT8fps1120012001200D0

Rows

PrecisionRuntimeInputPower modeSoftwareMetricClassDateSourceDerivationDupes
INT8hailo sdk (inferred)300x300 b8default1200 fpsD2024-Q1EdgeAIStack · edgeaistack:benchmark-corpus · Estimated from Hailo-8L 13 TOPS budget and SSD-MobileNetV1 FLOPs (2.3B), lightweight model benefits from Hailo architect · verified 2026-09-07Estimated from Hailo-8L 13 TOPS budget and SSD-MobileNetV1 FLOPs (2.3B), lightweight model benefits from Hailo architecture0

Cross-hardware comparison

Best row per hardware for the same model and precision, relative to the fastest.

HardwareBest valueClass
Hailo-8L1200 fps
D
Google Coral Edge TPU153.8 fps
C

Assumptions

  • Rows from the research corpus do not state a runtime; the platform's native runtime (TensorRT / Edge TPU / Hailo SDK / RKNN / CPU) is assumed and flagged runtime_inferred.
  • Class C = measured and published by the source named on the row; class D = EdgeAIStack-derived (derivation stated). Rows are inference-only unless scope says end_to_end; publisher measurement conditions (JetPack, batch, warm-up) are in the linked page.

Warnings

  • 1 of 1 matching rows are EdgeAIStack-derived (class D); treat them as estimates until a measured row (class C) or your own measurement replaces them.

Method and limitations

Rows are read from the normalised benchmark database (publisher benchmarks and research-derived rows, deduplicated per hardware × model × runtime × precision × input × power mode, best evidence kept). Expected range = min / median / max of the matching rows per precision; when a precision has no row the estimator's benchmark hierarchy (B → C → D) is consulted and its tier chain reported. Comparison = best row per hardware for the same model and precision, relative to the fastest. Nothing is scored; every number carries its class and source line.

Full method, dedupe rule, evidence classes and the confidence rule: Benchmark Explorer methodology.

Measure it yourself.

Nothing measured for your exact config, or want to confirm a class-D row? Run the measurement protocol on your board and submit the result — a human checks it against the protocol before it becomes a class-C row with your attribution.

SUBMIT A MEASUREMENT →

Change one input and re-run.

The live engine keeps every source line and gives you a fresh permalink and summary.

OPEN THIS QUERY LIVE →