on

Can the NVIDIA Jetson Orin Nano 4GB (4 GB) run MiniCPM5 2B?

50Fair quality (C) · 50 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well (tight fit)

Runs well (tight fit). At Q3_K_M it needs about 2.4 GB of 2.4 GB usable, with an estimated speed of 32.1 tok/s.

Best quant
Q3_K_M
Generation speed
32.1 tok/s
Prompt processing
300 tok/s
First token (1K prompt)
3.4 s
Largest safe context
8K

Best app to run it on the NVIDIA Jetson Orin Nano 4GB (4 GB)

On Linux on ARM boards

LM Studio

Desktop app · runs on llama.cpp, MLX

  • Point-and-click: search, download and chat in one window.

Open MiniCPM5 2B in LM Studio

  • llama.cpp Usually the first to support new model architectures.
  • Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

Want an agent? MiniCPM5 2B supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download MiniCPM5 2B

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

huggingface.co/openbmb/MiniCPM5-2B-GGUF (opens in a new tab)

ollama run hf.co/openbmb/MiniCPM5-2B-GGUF

Original weights · Hugging Face

Full-precision files from OpenBMB, for fine-tuning, vLLM, Transformers.

huggingface.co/openbmb/MiniCPM5-2B (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from OpenBMB. The weights themselves download from Hugging Face.

github.com/OpenBMB/MiniCPM (opens in a new tab)

OpenBMB's official MiniCPM repo, with deployment guides for the MiniCPM5 series.

git clone https://github.com/OpenBMB/MiniCPM

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 50Fair quality (C) · 50 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q3_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs welltight fit
How well it runs on the NVIDIA Jetson Orin Nano 4GB (4 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.22.7 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.24.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.13.4 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score75.1 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the NVIDIA Jetson Orin Nano 4GB (4 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 2.2 GB 2.4 GB 40.8 tok/s Runs welltight fit 42Fair quality (C) · 42 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 2.4 GB 2.4 GB 32.1 tok/s Runs welltight fit 50Fair quality (C) · 50 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 2.7 GB 2.4 GB 21.1 tok/s Slowfar over GPU memory limit 57Good quality (B) · 57 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 2.9 GB 2.4 GB 17.4 tok/s Slowfar over GPU memory limit 58Good quality (B) · 58 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 3.2 GB 2.4 GB — Won't run 59Good quality (B) · 59 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 3.8 GB 2.4 GB — Won't run 60Good quality (B) · 60 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 6.2 GB 2.4 GB — Won't run 60Good quality (B) · 60 of 100: how capable the model is at F16, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

Quick answers

How much memory does MiniCPM5 2B need on the NVIDIA Jetson Orin Nano 4GB 4GB?

At Q3_K_M it needs about 2.4 GB. The NVIDIA Jetson Orin Nano 4GB 4GB has 2.4 GB usable.

How fast is MiniCPM5 2B on the NVIDIA Jetson Orin Nano 4GB 4GB?

About 32.1 tok/s at Q3_K_M, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of MiniCPM5 2B should I use on the NVIDIA Jetson Orin Nano 4GB 4GB?

Q3_K_M. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.

Was this page helpful?