Check my GPU

on

Can the NVIDIA GeForce RTX 5060 Ti 16GB run MiMo-VL 7B RL?

79 ptsGreat (A) · 79 of 100 points: Model quality 25.8/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 13.6/15

Yes, it runs well

Runs well. At Q6_K it needs about 9.4 GB of 16.0 GB usable, with an estimated speed of 45.9 tok/s.

Best quant
Q6_K
Generation speed
45.9 tok/s
Prompt processing
2,053 tok/s
First token (1K prompt)
0.5 s
Largest safe context
51K

Download MiMo-VL 7B RL

Quantized files · GGUF

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

huggingface.co/XiaomiMiMo/MiMo-VL-7B-RL-GGUF (opens in a new tab)

ollama run hf.co/XiaomiMiMo/MiMo-VL-7B-RL-GGUF

Original weights · Hugging Face

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

huggingface.co/XiaomiMiMo/MiMo-VL-7B-RL (opens in a new tab)

No sign-in needed.

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

How the A grade is scored

Every result gets up to 100 points from four parts. The points decide the letter grade.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.25.8 / 45
Memory fitFull marks when everything sits in GPU or unified memory; fewer when part spills to system RAM.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.13.6 / 15
Total79.4 / 10079 ptsGreat (A) · 79 of 100 points: Model quality 25.8/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 13.6/15

Grade scale: S 85+ · A 72+ · B 58+ · C 42+ · D 25+ · F under 25 points.

Every quantization on the NVIDIA GeForce RTX 5060 Ti 16GB

Quant Memory needed Available Speed Fit Grade · points Download
Q2_K 5.9 GB 16.0 GB 109 tok/s Runs well 66 ptsGood (B) · 66 of 100 points: Model quality 18.3/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 8.6/15 GGUF files (opens in a new tab)
Q3_K_M 6.7 GB 16.0 GB 85.6 tok/s Runs well 71 ptsGood (B) · 71 of 100 points: Model quality 21.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 9.6/15 GGUF files (opens in a new tab)
Q4_K_M 7.7 GB 16.0 GB 66.2 tok/s Runs well 75 ptsGreat (A) · 75 of 100 points: Model quality 24.8/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 11.1/15 GGUF files (opens in a new tab)
Q5_K_M 8.5 GB 16.0 GB 54.7 tok/s Runs well 77 ptsGreat (A) · 77 of 100 points: Model quality 25.3/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 12.3/15 GGUF files (opens in a new tab)
Q6_K 9.4 GB 16.0 GB 45.9 tok/s Runs well 79 ptsGreat (A) · 79 of 100 points: Model quality 25.8/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 13.6/15 GGUF files (opens in a new tab)
Q8_0 11.4 GB 16.0 GB 33.7 tok/s Runs well 79 ptsGreat (A) · 79 of 100 points: Model quality 26.1/45, Memory fit 25.0/25, Speed 13.8/15, Memory use 15.0/15 GGUF files (opens in a new tab)
F16 19.2 GB 16.0 GB 7.4 tok/s Runs with offload 57 ptsUsable (C) · 57 of 100 points: Model quality 26.1/45, Memory fit 10.0/25, Speed 6.4/15, Memory use 15.0/15 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

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.