on

Can the Intel Xeon Silver (4100 to 4300 series) NAS (256 GB) run Chandra OCR 2?

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

Yes, it runs well

Runs well. At Q4_K_M it needs about 22.5 GB of 230 GB usable, with an estimated speed of 12.9 tok/s.

Best quant
Q4_K_M
Generation speed
12.9 tok/s
Prompt processing
66.0 tok/s
First token (1K prompt)
15.5 s
Largest safe context
256K

Best app to run it on the Intel Xeon Silver (4100 to 4300 series) NAS (256 GB)

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Usually the first to support new model architectures.
llama-server -hf mradermacher/chandra-ocr-2-GGUF:Q4_K_M

How we choose: the files published for this model, which apps run in a container on a NAS without a graphics card (models run on its processor), and whether the model fits fully in the memory models can use. Details.

Download Chandra OCR 2

Recommended for the Intel Xeon Silver (4100 to 4300 series) NAS (256 GB): Q4_K_M. Every other quantization has its own download link in the table below.

Quantized files · GGUF

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

Download the Q4_K_M file (opens in a new tab)

huggingface.co/mradermacher/chandra-ocr-2-GGUF (opens in a new tab)

ollama run hf.co/mradermacher/chandra-ocr-2-GGUF:Q4_K_M

Original weights · Hugging Face

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

huggingface.co/datalab-to/chandra-ocr-2 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/datalab-to/chandra (opens in a new tab)

git clone https://github.com/datalab-to/chandra

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

How it’s rated

Quality 45Fair quality (C) · 45 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q4_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 well
How well it runs on the Intel Xeon Silver (4100 to 4300 series) NAS (256 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.20.5 / 45
Memory fitFull marks when the model fits in the share of the NAS’s memory that models can use (the rest stays with the NAS system and its storage services); fewer when it goes past that limit.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.8.5 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.2.3 / 15
Match score56.3 / 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 Xeon Silver (4100 to 4300 series) NAS (256 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 21.4 GB 230 GB 21.3 tok/s Runs well 33Basic quality (D) · 33 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 21.9 GB 230 GB 16.7 tok/s Runs well 40Fair quality (C) · 40 of 100: how capable the model is at Q3_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)
Q4_K_M 22.5 GB 230 GB 12.9 tok/s Runs well 45Fair quality (C) · 45 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 23.1 GB 230 GB 10.7 tok/s Runs well 46Fair quality (C) · 46 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 23.6 GB 230 GB 9.0 tok/s Slow 47Fair quality (C) · 47 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 24.9 GB 230 GB 6.6 tok/s Slow 48Fair quality (C) · 48 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 29.9 GB 230 GB 3.0 tok/s Slow 48Fair quality (C) · 48 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. 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.

Was this page helpful?