HomeBenchmarksHailo-8L › YOLOv8n
Benchmark Explorer · YOLOv8n on Hailo-8L

YOLOv8n on Hailo-8L: 2 rows.

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

yolov8n on Hailo-8L: 2 rows (2 measured, 0 derived). Expected: INT8 53–65 fps. Fastest: NVIDIA A100 (server) 1010.1 fps (class C), Jetson Thor T5000 859 fps (class D), NVIDIA L4 (24GB) 816 fps (class D).

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
INT8fps2535965C2

Rows

PrecisionRuntimeInputPower modeSoftwareMetricClassDateSourceDerivationDupes
INT8hailo sdk (inferred)640x640 b1default65 fpsC2024-Q2Hailo (community examples) · github:hailo-ai/hailo-rpi5-examples · verified 2026-09-071
INT8hailo sdk (inferred)640x640 b8default53 fpsC2024-Q1Hailo · github:hailo-ai/hailo_model_zoo/HAILO8L_object_detection · verified 2026-09-071

Cross-hardware comparison

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

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.

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 →