HomeBenchmarksJetson Thor T5000 › YOLO11m
Benchmark Explorer · YOLO11m on Jetson Thor T5000

YOLO11m on Jetson Thor T5000: 3 rows.

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

yolo11_posem on Jetson Thor T5000: 3 rows (0 measured, 3 derived). Expected: FP16 269 fps; FP8 369 fps; INT8 328 fps. Fastest: Jetson Thor T5000 369 fps (class D), Hailo-8 47.7 fps (class D), Hailo-8L 34 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
FP16fps1269269269D0
FP8fps1369369369D0
INT8fps1328328328D0

Rows

PrecisionRuntimeInputPower modeSoftwareMetricClassDateSourceDerivationDupes
FP8tensorrt640x640 b1130wsdk v1369 fpsD2026EdgeAIStack · edgeaistack:benchmark-corpus · Thor Seg+Pose · verified 2026-09-07Thor Seg+Pose0
INT8tensorrt640x640 b1130wsdk v1328 fpsD2026EdgeAIStack · edgeaistack:benchmark-corpus · Thor Seg+Pose · verified 2026-09-07Thor Seg+Pose0
FP16tensorrt640x640 b1130wsdk v1269 fpsD2026EdgeAIStack · edgeaistack:benchmark-corpus · Thor Seg+Pose · verified 2026-09-07Thor Seg+Pose0

Cross-hardware comparison

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

HardwareBest valueClass
Jetson Thor T5000369 fps
D
Hailo-847.7 fps
D
Hailo-8L34 fps
D

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.

Warnings

  • 3 of 3 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.

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 →