on

Can the NVIDIA L40S run MiMo-VL 7B RL?

58Good quality (B) · 58 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At Q8_0 it needs about 13.0 GB of 48.0 GB usable, with an estimated speed of 65.0 tok/s.

Best quant
Q8_0
Generation speed
65.0 tok/s
Prompt processing
7,936 tok/s
First token (1K prompt)
0.3 s
Largest safe context
125K

Best app to run it on the NVIDIA L40S

On Linux

vLLM

Inference server · runs on vLLM

  • The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
vllm serve XiaomiMiMo/MiMo-VL-7B-RL
  • LM Studio Point-and-click: search, download and chat in one window.
  • SGLang The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.

On Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

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

Open MiMo-VL 7B RL in LM Studio

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

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 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 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 58Good quality (B) · 58 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q8_0, 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 great
How well it runs on the NVIDIA L40S: 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.26.1 / 45
Memory fitFull marks when everything sits in GPU 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.6.3 / 15
Match score72.4 / 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 L40S

Quant Memory needed Available Speed Runs Quality Download
Q2_K 7.5 GB 48.0 GB 210 tok/s Runs great 40Fair quality (C) · 40 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 8.3 GB 48.0 GB 165 tok/s Runs great 48Fair quality (C) · 48 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 9.3 GB 48.0 GB 128 tok/s Runs great 55Good quality (B) · 55 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q5_K_M 10.1 GB 48.0 GB 105 tok/s Runs great 56Good quality (B) · 56 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 11.0 GB 48.0 GB 88.6 tok/s Runs great 57Good quality (B) · 57 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 13.0 GB 48.0 GB 65.0 tok/s Runs great 58Good quality (B) · 58 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
F16 20.8 GB 48.0 GB 29.9 tok/s Runs well 58Good quality (B) · 58 of 100: how capable the model is at F16, whatever it runs on. Match score 74/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 MiMo-VL 7B RL need on the NVIDIA L40S 48GB?

At Q8_0 it needs about 13.0 GB. The NVIDIA L40S 48GB has 48.0 GB usable.

How fast is MiMo-VL 7B RL on the NVIDIA L40S 48GB?

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

Which quantization of MiMo-VL 7B RL should I use on the NVIDIA L40S 48GB?

Q8_0. 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?