Image Segmentation
LiteRT
LiteRT
android
on-device
gpu
semantic-segmentation
cityscapes
real-time
pidnet
Instructions to use litert-community/PIDNet-S-Cityscapes-LiteRT with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- LiteRT
How to use litert-community/PIDNet-S-Cityscapes-LiteRT with LiteRT:
# No code snippets available yet for this library. # To use this model, check the repository files and the library's documentation. # Want to help? PRs adding snippets are welcome at: # https://github.com/huggingface/huggingface.js
- Notebooks
- Google Colab
- Kaggle
Add measured Snapdragon NPU / GPU section (Galaxy S26)
Browse filesNumbers from the 2026-08-23 Galaxy S26 sweep. Primary log:
litertlm-convert/portal_work/bench_all.txt + bench_redo.txt, summarised in
portal_work/NOTES.md (2026-08-23, the 50-model NPU/GPU comparison).
Every row carries device, SoC, runtime, N and thermal state. Measurements
are joined to this repo by exact .tflite file name.
README.md
CHANGED
|
@@ -103,6 +103,19 @@ Measured on a **Pixel 8a** (Tensor G3, Android 16) with the standard TFLite [`be
|
|
| 103 |
|
| 104 |
**Any on-device figure recorded when this model shipped came from a different runtime.** It was taken through LiteRT's own `CompiledModel` accelerator (logcat reports it as `LITERT_CL`), which is the path the Kotlin sample app and the LiteRT API use, and it appears elsewhere on this card. The rows above are the classic TFLite OpenCL delegate, measured with a tool anyone can download and re-run. The two are not comparable, so read the rows above as a reproducible floor rather than as this model's speed on LiteRT.
|
| 105 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 106 |
## License
|
| 107 |
|
| 108 |
MIT (PIDNet / XuJiacong/PIDNet). Cityscapes label taxonomy from the Cityscapes dataset.
|
|
|
|
| 103 |
|
| 104 |
**Any on-device figure recorded when this model shipped came from a different runtime.** It was taken through LiteRT's own `CompiledModel` accelerator (logcat reports it as `LITERT_CL`), which is the path the Kotlin sample app and the LiteRT API use, and it appears elsewhere on this card. The rows above are the classic TFLite OpenCL delegate, measured with a tool anyone can download and re-run. The two are not comparable, so read the rows above as a reproducible floor rather than as this model's speed on LiteRT.
|
| 105 |
|
| 106 |
+
## Snapdragon NPU (Hexagon)
|
| 107 |
+
|
| 108 |
+
The NPU is **2.95x faster** than the GPU (5.48 ms against 16.20 ms) and loads 12.62x faster (119 ms against 1502 ms).
|
| 109 |
+
|
| 110 |
+
| backend | inference (median / min) | load |
|
| 111 |
+
|---|---:|---:|
|
| 112 |
+
| NPU (Hexagon v81) | 5.48 ms / 5.44 ms | 119 ms |
|
| 113 |
+
| GPU (Adreno) | 16.20 ms / 15.73 ms | 1502 ms |
|
| 114 |
+
|
| 115 |
+
Measured on a **Samsung Galaxy S26** (Snapdragon 8 Elite Gen 5 / SM8850, Hexagon v81, Android 16), LiteRT `CompiledModel` 2.2.0, one accelerator per process, 5 warm-up runs then N=50 timed runs, median reported. Every run held thermal status `NONE` throughout. Headroom 0.67, where 1.0 is the throttling threshold.
|
| 116 |
+
|
| 117 |
+
The NPU rows here ran artifacts compiled ahead of time for SM8850 with QAIRT 2.47.0; the GPU rows ran the published files as they are. LiteRT can also compile for the NPU on the device at first load, which is what lets you ship the published file unchanged — that path and the ten runtime libraries it needs are in the [NPU recipe](https://github.com/john-rocky/hf-to-litertlm/blob/main/docs/android-npu.md), and we did not measure it here. GPU wiring is in the [GPU recipe](https://github.com/john-rocky/hf-to-litertlm/blob/main/docs/android-gpu.md).
|
| 118 |
+
|
| 119 |
## License
|
| 120 |
|
| 121 |
MIT (PIDNet / XuJiacong/PIDNet). Cityscapes label taxonomy from the Cityscapes dataset.
|