HomeBenchmarksJetson Orin Nano 8GB › Whisper Tiny En
Benchmark Explorer · Whisper Tiny En on Jetson Orin Nano 8GB

Whisper Tiny En on Jetson Orin Nano 8GB: 2 rows.

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

whispertiny-en on Jetson Orin Nano 8GB: 2 rows (2 measured, 0 derived). Expected: FP16 640 ms; FP32 1740 ms.

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
FP16ms1640640640C1
FP32ms1174017401740C1

Rows

PrecisionRuntimeInputPower modeSoftwareMetricClassDateSourceDerivationDupes
FP32tensorrt (inferred)n/a b1default1740 msC2024-Q1NVIDIA (NVIDIA-AI-IOT) · github:NVIDIA-AI-IOT/whisper_trt · verified 2026-09-070
FP16tensorrt (inferred)n/a b1default640 msC2024-Q1NVIDIA (NVIDIA-AI-IOT) · github:NVIDIA-AI-IOT/whisper_trt · verified 2026-09-070

Cross-hardware comparison

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

HardwareBest valueClass
Jetson Orin Nano 8GB1740 ms
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.

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 →