Instructions to use litert-community/Qwen2.5-Coder-3B-Instruct with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- LiteRT-LM
How to use litert-community/Qwen2.5-Coder-3B-Instruct with LiteRT-LM:
# LiteRT-LM runs on various platforms (Android, iOS, Windows, Linux, macOS, IoT, Web/WASM) # and supports many APIs (C++, Python, Kotlin, Swift, JavaScript, Flutter). # For platform-specific integration guides, please refer to the official developer website: # https://ai.google.dev/edge/litert-lm # To try LiteRT-LM, the easiest way is to use our CLI tool. # 1. Install the LiteRT-LM CLI tool: pip install -U litert-lm # 2. Download and run this model locally: # See: https://ai.google.dev/edge/litert-lm/cli litert-lm run \ --from-huggingface-repo=litert-community/Qwen2.5-Coder-3B-Instruct \ --prompt="Write me a poem"
- Notebooks
- Google Colab
- Kaggle
language:
- en
license: apache-2.0
license_link: https://huggingface.co/Qwen/Qwen2.5-Coder-3B-Instruct/blob/main/LICENSE
pipeline_tag: text-generation
base_model: Qwen2.5-Coder-3B-Instruct
base_model_relation: quantized
library_name: litert-lm
tags:
- litert-lm
- litertlm
- qwen
- Qwen2.5
Qwen2.5-Coder-3B-Instruct LiteRT-LM Model
This repository contains LiteRT-LM variant of Qwen/Qwen2.5-Coder-3B-Instruct optimized for on-device text generation.
Available Artifact
| File | Quantization Recipe | Context | Size |
|---|---|---|---|
Qwen2.5_Coder_3B_It.litertlm |
dynamic_wi8_afp32 | - | 3.4 GB |
Integration
Ready to integrate this into your product? Get started in the LiteRT-LM documentation.
Performance (measured)
Apple M4 Max
Measured with the LiteRT-LM CLI: litert-lm benchmark -p 256 -d 256 --runs 3 --cache no
(litert-lm 0.15.0) on an idle Apple M4 Max (macOS); 256 prefill / 256 decode tokens, 3 iterations
averaged by the tool. A desktop reference point β phone-side figures vary by SoC and backend.
| Backend | Prefill (tokens/s) | Decode (tokens/s) | Time-to-first-token (s) |
|---|---|---|---|
| CPU | 121 | 26.7 | 2.16 |
| GPU | 1,320 | 77.8 | 0.21 |
Galaxy S26 β GPU vs CPU (litert-lm 0.16.0)
Measured on a physical Samsung Galaxy S26 (SM-S942Q, Snapdragon 8 Elite Gen 5 / SM8850, Android 16) with litert_lm_advanced_main from the litert-lm v0.16.0 release; the GPU backend is OpenCL (LITERT_CL). One fixed 205-token prompt text (223 tokens under this tokenizer), --benchmark. Two runs per backend taken back-to-back β cells show the range. Peak RSS is the process VmHWM. Before quoting, the same file was run on each backend with a real prompt: both backends produced a correct text answer.
| Backend | Prefill (223 tok) | Decode | Time-to-first-token | Init | Peak RSS |
|---|---|---|---|---|---|
| GPU (OpenCL) | 403β423 tok/s | 16.3β16.5 tok/s | 0.59β0.61 s | 4.3β4.9 s | 864 MB |
| CPU (XNNPACK) | 159β187 tok/s | 12.1β13.6 tok/s | 1.26β1.49 s | 3.6β4.6 s | 3934 MB |
The GPU takes the whole graph β decode 1603/1603 ops and prefill 1452/1452 on LITERT_CL. It wins prefill 2.2β2.7Γ and decode 1.2β1.4Γ, and peaks 4.6Γ lower (864 against 3934 MB) β for a 3.4 GB int8 bundle the RSS difference is the practical headline.