Benchmark Explorer · YOLO11n on Jetson Orin Nano Super

YOLO11n on Jetson Orin Nano Super: 3 rows.

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

yolo11n on Jetson Orin Nano Super: 3 rows (2 measured, 1 derived). Expected: FP16 221 fps; FP32 52 fps; INT8 270 fps. Fastest: NVIDIA L40S (48GB) 2760 fps (class D), Jetson Thor T5000 1150 fps (class D), NVIDIA L4 (24GB) 1150 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
FP16fps1221221221C1
FP32fps1525252D0
INT8fps1270270270C1

Rows

PrecisionRuntimeInputPower modeSoftwareMetricClassDateSourceDerivationDupes
INT8tensorrt640x640 b115wultralytics 8.3.x270 fpsC2024Ultralytics · bench:ultralytics-yolo11-jetson 8.3.x · verified 2026-09-073
FP16tensorrt640x640 b115wultralytics 8.3.x221 fpsC2024Ultralytics · bench:ultralytics-yolo11-jetson 8.3.x · verified 2026-09-073
FP32tensorrt640x640 b1maxnsdk v152 fpsD2026EdgeAIStack · edgeaistack:benchmark-corpus · FP32 Benchmarks · verified 2026-09-07FP32 Benchmarks0

Cross-hardware comparison

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

Assumptions

  • 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 →