on

Can the Intel Xeon W-2100 series NAS (256 GB) run LLM4Decompile 9B V2?

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

Yes, it runs well

Runs well. At Q2_K it needs about 23.4 GB of 230 GB usable, with an estimated speed of 12.2 tok/s.

Best quant
Q2_K
Generation speed
12.2 tok/s
Prompt processing
40.8 tok/s
First token (1K prompt)
25.1 s
Largest safe context
128K

Best app to run it on the Intel Xeon W-2100 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/llm4decompile-9b-v2-GGUF:Q2_K

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 LLM4Decompile 9B V2

Recommended for the Intel Xeon W-2100 series NAS (256 GB): Q2_K. 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 Q2_K file (opens in a new tab)

huggingface.co/mradermacher/llm4decompile-9b-v2-GGUF (opens in a new tab)

ollama run hf.co/mradermacher/llm4decompile-9b-v2-GGUF:Q2_K

Original weights · Hugging Face

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

huggingface.co/LLM4Binary/llm4decompile-9b-v2 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/albertan017/LLM4Decompile (opens in a new tab)

Official code and the Ghidra script that feeds decompiler output to the V2 models.

git clone https://github.com/albertan017/LLM4Decompile

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

How it’s rated

Quality 26Basic quality (D) · 26 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 47/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q2_K, 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 W-2100 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.12.0 / 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.3 / 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 score47.6 / 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 W-2100 series NAS (256 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 23.4 GB 230 GB 12.2 tok/s Runs well 26Basic quality (D) · 26 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 47/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 24.2 GB 230 GB 9.6 tok/s Slow 31Basic quality (D) · 31 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 (opens in a new tab)
Q4_K_M 25.2 GB 230 GB 7.4 tok/s Slow 36Basic quality (D) · 36 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 (opens in a new tab)
Q5_K_M 26.1 GB 230 GB 6.1 tok/s Slow 36Basic quality (D) · 36 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 50/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 27.1 GB 230 GB 5.1 tok/s Slow 37Basic quality (D) · 37 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 50/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 29.2 GB 230 GB 3.8 tok/s Slow 38Basic quality (D) · 38 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 49/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 37.5 GB 230 GB 1.7 tok/s Very slow 38Basic quality (D) · 38 of 100: how capable the model is at F16, whatever it runs on. Match score 48/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?