on

Can the Intel Core Ultra 7 255H / 9 285H NAS (64 GB) run Laguna XS 2.1 (33B-A3B)?

77Great quality (A) · 77 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At Q4_K_M it needs about 25.3 GB of 36.5 GB usable, with an estimated speed of 35.8 tok/s.

Best quant
Q4_K_M
Generation speed
35.8 tok/s
Prompt processing
2,147 tok/s
First token (1K prompt)
0.5 s
Largest safe context
74K

Best app to run it on the Intel Core Ultra 7 255H / 9 285H NAS (64 GB)

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Usually the first to support new model architectures.
llama-server -hf poolside/Laguna-XS-2.1-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 Laguna XS 2.1 (33B-A3B)

Recommended for the Intel Core Ultra 7 255H / 9 285H NAS (64 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/poolside/Laguna-XS-2.1-GGUF (opens in a new tab)

ollama run hf.co/poolside/Laguna-XS-2.1-GGUF:Q4_K_M

Original weights · Hugging Face

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

huggingface.co/poolside/Laguna-XS-2.1 (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 77Great quality (A) · 77 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 89/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 great
How well it runs on the Intel Core Ultra 7 255H / 9 285H NAS (64 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.35.1 / 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.14.2 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score89.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 Core Ultra 7 255H / 9 285H NAS (64 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 18.2 GB 36.5 GB 55.3 tok/s Runs great 57Good quality (B) · 57 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 21.2 GB 36.5 GB 45.0 tok/s Runs great 68Good quality (B) · 68 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 25.3 GB 36.5 GB 35.8 tok/s Runs great 77Great quality (A) · 77 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 28.6 GB 36.5 GB 30.1 tok/s Runs great 79Great quality (A) · 79 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 32.3 GB 36.5 GB 25.6 tok/s Runs welltight fit 81Great quality (A) · 81 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 40.3 GB 36.5 GB 16.3 tok/s Slowfar over GPU memory limit 82Great quality (A) · 82 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
F16 71.7 GB 36.5 GB — Won't run 82Great quality (A) · 82 of 100: how capable the model is at F16, whatever it runs on. Match score 11/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 Laguna XS 2.1 (33B-A3B) need on the Intel Core Ultra 7 255H / 9 285H NAS 64GB?

At Q4_K_M it needs about 25.3 GB. The Intel Core Ultra 7 255H / 9 285H NAS 64GB has 36.5 GB usable.

How fast is Laguna XS 2.1 (33B-A3B) on the Intel Core Ultra 7 255H / 9 285H NAS 64GB?

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

Which quantization of Laguna XS 2.1 (33B-A3B) should I use on the Intel Core Ultra 7 255H / 9 285H NAS 64GB?

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