on

Can the Intel Arc A580 run surya ocr 2.5?

15Basic quality (D) · 15 of 100: how capable the model is at F16, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At F16 it needs about 2.5 GB of 8.0 GB usable, with an estimated speed of 163 tok/s.

Best quant
F16
Generation speed
163 tok/s
Prompt processing
19,609 tok/s
First token (1K prompt)
0.3 s
Largest safe context
256K

Best app to run it on the Intel Arc A580

On Windows

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf datalab-to/surya-ocr-2.5-gguf:F16
  • LM Studio Point-and-click: search, download and chat in one window.
  • Jan Point-and-click: search, download and chat in one window.

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf datalab-to/surya-ocr-2.5-gguf:F16
  • LM Studio Point-and-click: search, download and chat in one window.
  • Jan Point-and-click: search, download and chat in one window.

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 surya ocr 2.5

Quantized files · GGUF

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

huggingface.co/datalab-to/surya-ocr-2.5-gguf (opens in a new tab)

ollama run hf.co/datalab-to/surya-ocr-2.5-gguf

Original weights · Hugging Face

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

huggingface.co/datalab-to/surya-ocr-2.5 (opens in a new tab)

No sign-in needed.

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 15Basic quality (D) · 15 of 100: how capable the model is at F16, whatever it runs on. Match score 53/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 Intel Arc A580: 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.6.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.7.2 / 15
Match score53.9 / 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 Intel Arc A580

Quant Memory needed Available Speed Runs Quality Download
Q2_K 1.4 GB 8.0 GB 1,143 tok/s Runs great 10Basic quality (D) · 10 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 48/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 1.4 GB 8.0 GB 900 tok/s Runs great 12Basic quality (D) · 12 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 49/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 1.5 GB 8.0 GB 696 tok/s Runs great 14Basic quality (D) · 14 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 50/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q5_K_M 1.6 GB 8.0 GB 575 tok/s Runs great 14Basic quality (D) · 14 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 1.7 GB 8.0 GB 483 tok/s Runs great 14Basic quality (D) · 14 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 1.8 GB 8.0 GB 354 tok/s Runs great 15Basic quality (D) · 15 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 52/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 2.5 GB 8.0 GB 163 tok/s Runs great 15Basic quality (D) · 15 of 100: how capable the model is at F16, whatever it runs on. Match score 53/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

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?