Home › Benchmarks › Rockchip RK3568 › MobileNetV2v2
Benchmark Explorer · MobileNetV2v2 on Rockchip RK3568

MobileNetV2v2 on Rockchip RK3568: 1 row.

Method v1.4.1 · dataset 2026-09-29 · verified 2026-09-16 · last updated September 2026

mobilenetv2v2 on Rockchip RK3568: 1 row (1 measured, 0 derived). Measured share for this scope: 100% of 1 row (class C). Expected: INT8 180.7 fps. Fastest: Jetson Thor T5000 4004 fps (class D), Hailo-10H 2944 fps (class D), Hailo-8 2597 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
INT8fps1180.7180.7180.7C1

Rows

PrecisionRuntimeInputPower modeSoftwareMetricClassDateSourceDerivationDupes
INT8rknn224x224 b1—sdk rknn_model_zoo v2.3.2180.7 fpsC2025Rockchip · bench:rockchip-airockchip-official-github-org-rknn-model-zoo-official-benchmark-table-readme-md rknn_model_zoo v2.3.2 · verified 2026-09-280

Cross-hardware comparison

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

HardwareBest valueClass
Jetson Thor T50004004 fps
D
Hailo-10H2944 fps
D
Hailo-82597 fps
C
Hailo-8L1738 fps
C
Jetson Orin Nano Super1280.4 fps
C
Jetson Orin NX 16GB1250 fps
D
Rockchip RK3588 NPU450.7 fps
C
Rockchip RK3588S450.7 fps
D
Rockchip RK3568180.7 fps
C

Assumptions

  • Latency provenance: 1 of the 1 matching rows that report a latency computed it as 1000/fps rather than measuring it (latency_source → derived_reciprocal); 0 were observed independently. Every p99 in the database is a modelled 1.20–1.43× tail over the p50, never an observed one.
  • 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 →