YOLOv5s on Hailo-8L: 2 rows.
Method v1.0 · dataset 2026-09-07 · verified 2026-09-07 · last updated September 2026
yolov5s on Hailo-8L: 2 rows (1 measured, 1 derived). Expected: INT8 68–124 fps. Fastest: Hailo-8 543 fps (class D), Hailo-10H 249 fps (class D), Hailo-8L 124 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.
| Precision | Metric | N | Min | Median | Max | Best class | Measured |
|---|---|---|---|---|---|---|---|
| INT8 | fps | 2 | 68 | 96 | 124 | C | 1 |
Rows
| Precision | Runtime | Input | Power mode | Software | Metric | Class | Date | Source | Derivation | Dupes |
|---|---|---|---|---|---|---|---|---|---|---|
| INT8 | hailo sdk | 640x640 b1 | default | sdk v1 | 124 fps | D | 2026 | EdgeAIStack · edgeaistack:benchmark-corpus · Hailo Non-YOLO Benchmarks · verified 2026-09-07 | Hailo Non-YOLO Benchmarks | 0 |
| INT8 | hailo sdk (inferred) | 640x640 b8 | default | — | 68 fps | C | 2024-Q1 | Hailo · github:hailo-ai/hailo_model_zoo/HAILO8L_object_detection · verified 2026-09-07 | 0 |
Cross-hardware comparison
Best row per hardware for the same model and precision, relative to the fastest.
| Hardware | Best value | Class |
|---|---|---|
| Hailo-8 | 543 fps | D |
| Hailo-10H | 249 fps | D |
| Hailo-8L | 124 fps | D |
| Rockchip RK3588 NPU | 46.5 fps | D |
| Neousys Nuvo-9531 (Intel 12th-14th Gen Core) | 12 fps | D |
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 2 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.
Links
- Live engine (this exact query): https://edgeaistack.ai/engines/benchmark-explorer/?hw=hailo_8l&model=yolov5&variant=s&mv=1.0&dv=2026-09-07
- Methodology: /methodology/benchmark-explorer/
- Measurement protocol: /methodology/measurement-protocol/
- Dataset: /datasets/benchmarks-v2.json
- Hailo-8L overview: /benchmarks/hailo-8l/
Change one input and re-run.
The live engine keeps every source line and gives you a fresh permalink and summary.