on

Can the NVIDIA L40 run Unlimited OCR 2 (3B-A0.6B)?

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

Yes, it runs great

Runs great. At F16 it needs about 10.2 GB of 48.0 GB usable, with an estimated speed of 147 tok/s.

Best quant
F16
Generation speed
147 tok/s
Prompt processing
108,600 tok/s
First token (1K prompt)
0.3 s
Largest safe context
128K

Best app to run it on the NVIDIA L40

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 baidu/Unlimited-OCR-2
  • 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.
  • Docker Model Runner Handy if you already work in Docker.

On Windows

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.
  • On Windows it runs through WSL2.
vllm serve baidu/Unlimited-OCR-2
  • 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.
  • Docker Model Runner Handy if you already work in Docker.

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 Unlimited OCR 2 (3B-A0.6B)

Original weights · Hugging Face

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

huggingface.co/baidu/Unlimited-OCR-2 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/baidu/Unlimited-OCR (opens in a new tab)

git clone https://github.com/baidu/Unlimited-OCR

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

How it’s rated

Quality 44Fair quality (C) · 44 of 100: how capable the model is at F16, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at F16, 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 L40: 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.19.8 / 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.4.9 / 15
Match score64.7 / 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 L40

Quant Memory needed Available Speed Runs Quality Download
Q2_K 4.8 GB 48.0 GB 288 tok/s Runs great 30Basic quality (D) · 30 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q3_K_M 5.1 GB 48.0 GB 272 tok/s Runs great 36Basic quality (D) · 36 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q4_K_M 5.5 GB 48.0 GB 254 tok/s Runs great 41Fair quality (C) · 41 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q5_K_M 5.9 GB 48.0 GB 239 tok/s Runs great 42Fair quality (C) · 42 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q6_K 6.2 GB 48.0 GB 226 tok/s Runs great 43Fair quality (C) · 43 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
Q8_0 7.0 GB 48.0 GB 203 tok/s Runs great 44Fair quality (C) · 44 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 63/100 (quality, fit, speed and memory use) sets the ranking. All files (opens in a new tab)
F16 10.2 GB 48.0 GB 147 tok/s Runs great 44Fair quality (C) · 44 of 100: how capable the model is at F16, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. 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 Unlimited OCR 2 (3B-A0.6B) need on the NVIDIA L40 48GB?

At F16 it needs about 10.2 GB. The NVIDIA L40 48GB has 48.0 GB usable.

How fast is Unlimited OCR 2 (3B-A0.6B) on the NVIDIA L40 48GB?

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

Which quantization of Unlimited OCR 2 (3B-A0.6B) should I use on the NVIDIA L40 48GB?

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