Phi-3.5 MoE (42B-A6.6B) on Intel Core Ultra 5 225H NAS (32 GB)

Can the Intel Core Ultra 5 225H NAS (32 GB) run Phi-3.5 MoE (42B-A6.6B)?

Yes, it runs well (over GPU memory limit)

Runs well (over GPU memory limit). At Q2_K it needs about 19.9 GB of 18.2 GB usable, with an estimated speed of 23.6 tok/s.

Best quant: Q2_K
Generation speed: 23.6 tok/s
Prompt processing: 848 tok/s
First token (1K prompt): 1.2 s
Largest safe context: —

Best app to run it on the Intel Core Ultra 5 225H NAS (32 GB)

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

Splits the model between GPU memory and system RAM, which this setup needs.
Gives you direct control of how many layers sit on the GPU, the best way to squeeze a model that doesn’t quite fit.
Usually the first to support new model architectures.

llama-server -hf lmstudio-community/Phi-3.5-MoE-instruct-GGUF:Q2_K

Ollama Splits the model between GPU memory and system RAM, which this setup needs.
KoboldCpp Splits the model between GPU memory and system RAM, which this setup needs.

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 Phi-3.5 MoE (42B-A6.6B)

Quantized files · GGUF

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

huggingface.co/lmstudio-community/Phi-3.5-MoE-instruct-GGUF (opens in a new tab)

ollama run hf.co/lmstudio-community/Phi-3.5-MoE-instruct-GGUF

Original weights · Hugging Face

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

huggingface.co/microsoft/Phi-3.5-MoE-instruct (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/microsoft/PhiCookBook (opens in a new tab)

Microsoft’s official Phi cookbook: setup, inference and fine-tuning guides.

git clone https://github.com/microsoft/PhiCookBook

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

How it’s rated

Quality 39Basic quality (D) · 39 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 54/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 wellover GPU memory limit: How well it runs on the Intel Core Ultra 5 225H NAS (32 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.	17.6 / 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.	10.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	11.5 / 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 score	54.2 / 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 5 225H NAS (32 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	19.9 GB	18.2 GB	23.6 tok/s	Runs wellover GPU memory limit	39Basic quality (D) · 39 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q3_K_M`	23.6 GB	18.2 GB	—	Won't run	47Fair quality (C) · 47 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 6/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (Q3_K_L) (opens in a new tab)
`Q4_K_M`	28.7 GB	18.2 GB	—	Won't run	53Fair quality (C) · 53 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	32.9 GB	18.2 GB	—	Won't run	54Fair quality (C) · 54 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking.	GGUF files (opens in a new tab)
`Q6_K`	37.5 GB	18.2 GB	—	Won't run	55Good quality (B) · 55 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	47.5 GB	18.2 GB	—	Won't run	56Good quality (B) · 56 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	86.9 GB	18.2 GB	—	Won't run	56Good quality (B) · 56 of 100: how capable the model is at F16, whatever it runs on. Match score 7/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

55Good quality (B) · 55 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (64 GB) Q6_K · 49.8 tok/s · Runs great
55Good quality (B) · 55 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. Apple M1 Max (64 GB) Q6_K · 38.3 tok/s · Runs great
53Fair quality (C) · 53 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Pro (48 GB) Q4_K_M · 38.1 tok/s · Runs great
53Fair quality (C) · 53 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 Q4_K_M · 157 tok/s · Runs well (tight fit)
56Good quality (B) · 56 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell Q8_0 · 103 tok/s · Runs great
55Good quality (B) · 55 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (128 GB) Q6_K · 49.8 tok/s · Runs great

Quick answers

How much memory does Phi-3.5 MoE (42B-A6.6B) need on the Intel Core Ultra 5 225H NAS 32GB?

At Q2_K it needs about 19.9 GB. The Intel Core Ultra 5 225H NAS 32GB has 18.2 GB usable.

How fast is Phi-3.5 MoE (42B-A6.6B) on the Intel Core Ultra 5 225H NAS 32GB?

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

Which quantization of Phi-3.5 MoE (42B-A6.6B) should I use on the Intel Core Ultra 5 225H NAS 32GB?

Q2_K. 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.