Benchmark Explorer · YOLO11n on Jetson Orin Nano Super

YOLO11n on Jetson Orin Nano Super: 1 row.

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

yolo11_segn on Jetson Orin Nano Super: 1 row (1 measured, 0 derived). Measured share for this scope: 67% of 63 rows (class C). Expected: FP16 186.1 fps. Fastest: Jetson Thor T5000 530 fps (class C), Jetson AGX Orin 64GB 365.51 fps (class C), Jetson Orin Nano Super 186.1 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
FP16fps1186.1186.1186.1C1

Rows

PrecisionRuntimeInputPower modeSoftwareMetricClassDateSourceDerivationDupes
FP16tensorrt640x640 b1—tensorrt 10.3.0186.1 fpsC2026EdgeFirst AI · bench:edgefirst-yolo-validator-benchmarks-jetson-orin-nano-super-tensorrt-metrics 2026-06-22 · Ultralytics validator lane, latency_ms.inf · verified 2026-09-280

Cross-hardware comparison

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

Assumptions

  • Latency provenance: 0 of the 1 matching rows that report a latency computed it as 1000/fps rather than measuring it (latency_source → derived_reciprocal); 1 was 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 →