Model × hardware check
Can LFM3-1.7B run on AMD Ryzen AI Max+ 395 (Strix Halo) mini PC · 128 GB?
Yes, this is a comfortable estimate at 8,192 tokens. a tiny tri-hybrid model built for local agents, tool use, and structured outputs The Strix Halo mini PC provides 128 GB of shared memory, though firmware and OS allocation can leave substantially less usable by the GPU.
Short answer
Comfortable fit
At least 20% memory headroom remains after weights, KV cache, and runtime overhead.
- Available shared CPU/GPU memory
- 128 GB
- Estimated requirement
- 3.4 GB
- Headroom
- +124.6 GB
- Fit ratio
- 3713%
- Recommended quantization
- Q8_0
- Context ceiling
- 262,144 tokens
- Speed estimate
- Estimate · Very fast relative band
What the numbers say
The selected LFM3-1.7B package uses 1.8 GB of weight files. The 8K KV cache estimate is 0.1 GB, and the formula adds 1.5 GB of runtime overhead. That produces a 3.4 GB requirement against 128 GB of shared CPU/GPU memory.
usable GPU memory ~96-112GB depending on BIOS/OS; also 64GB variant This is a compact shared-memory system, not a dedicated-VRAM GPU. The audit warns that usable GPU memory may be roughly 96-112 GB depending on BIOS, OS, and allocation settings, so the full 128 GB should not be treated as universally available to one model.
The context ceiling shown above is the point where the same formula reaches the machine's capacity. It is not a promise that the backend can allocate that full context after the operating system and other applications take their share.
Quantization trade-offs at 8K
| Quantization | Weight files | 8K requirement | Fit on this machine | Context ceiling | Speed estimate | Ollama |
|---|---|---|---|---|---|---|
| QAD-Q4_0 | 1.05 GB | 2.7 GB | Comfortable fit · 4830% | 262,144 tokens | Estimate · Very fast relative band | ollama run lfm3:1.7b-qad-q4_0 |
| Q4_K_M | 1.10 GB | 2.7 GB | Comfortable fit · 4740% | 262,144 tokens | Estimate · Very fast relative band | ollama run lfm3:1.7b-q4_K_M |
| Q5_K_M | 1.26 GB | 2.9 GB | Comfortable fit · 4477% | 262,144 tokens | Estimate · Very fast relative band | No verified tag |
| Q6_K | 1.43 GB | 3.0 GB | Comfortable fit · 4227% | 262,144 tokens | Estimate · Very fast relative band | No verified tag |
| Q8_0 | 1.85 GB | 3.4 GB | Comfortable fit · 3713% | 262,144 tokens | Estimate · Very fast relative band | ollama run lfm3:1.7b-q8_0 |
Run commands
ollama run lfm3:1.7b-q8_0lms get "LFM3-1.7B"@q8_0
lms load <model-key-from-lms-ls> --gpu max --context-length 8192llama-cli -hf LiquidAI/LFM3-1.7B-GGUF --hf-file LFM3-1.7B-Q8_0.gguf -c 8192 -ngl 99 -p "Your prompt"mlx_lm.generate --model LiquidAI/LFM3-1.7B-MLX-4bit --prompt "Your prompt" --max-tokens 8192Commands are examples, not a guarantee that the selected quantization tag is available in every runtime. Confirm the package name and license on the linked model page.
If it does not fit
This pairing already clears the comfort threshold
The current estimate leaves +124.6 GB. A longer context or another GPU application can reduce that margin, so verify free memory before relying on it.
Low-cost setup upgrades
Useful upgrades around AMD Ryzen AI Max+ 395 (Strix Halo) mini PC · 128 GB
These are optional setup improvements, not a claim that an accessory can increase GPU or unified-memory capacity.
External NVMe SSD for model storage
Keeps large GGUF and MLX files off the boot drive. Fast storage reduces load time, but it does not increase the memory available for inference.
Search current listings on AmazonDesktop RAM upgrade kit
Useful for MoE CPU offload and keeping the operating system out of VRAM. Match the motherboard's memory type, slot layout, capacity limit, and validated part numbers.
Search current listings on AmazonGPU support bracket
A lower-cost mechanical upgrade for heavy three-slot cards. Check clearance, mounting height, and whether the bracket blocks fans or case panels.
Search current listings on AmazonAs an Amazon Associate I earn from qualifying purchases. Links are sponsored search links and do not change the price you pay. Affiliate disclosure.
Where this estimate can break
- Liquid AI positions this as a small agent and structured-output model, not a replacement for a larger coding or complex-reasoning model.
- The 256K context is a capacity limit; long agent traces still consume KV cache and can lower throughput.
- The official GGUF card requires Ollama v0.40.12 or newer for the LFM3 architecture.
- Other GPU applications, display buffers, and the operating system reduce usable memory.
- Longer prompts, concurrent requests, and a different backend can raise peak memory.
Compare this pairing
FAQ
Questions about this pairing.
How much memory does LFM3-1.7B need on AMD Ryzen AI Max+ 395 (Strix Halo) mini PC · 128 GB?
At an 8K context with Q8_0, the estimate is 3.4 GB: 1.8 GB of weights, 0.1 GB of KV cache, and 1.5 GB of runtime overhead. The available shared CPU/GPU memory is 128 GB.
What context length can AMD Ryzen AI Max+ 395 (Strix Halo) mini PC · 128 GB handle with this model?
The calculated ceiling is 262,144 tokens for this quantization, capped by the model's native 262,144-token context. Actual usable context can be lower after the OS, other applications, and backend workspace.
How does quantization change the memory requirement on AMD Ryzen AI Max+ 395 (Strix Halo) mini PC · 128 GB?
At 8,192 tokens, the published variants calculate as follows: QAD-Q4_0: 2.7 GB, comfortable fit; Q4_K_M: 2.7 GB, comfortable fit; Q5_K_M: 2.9 GB, comfortable fit; Q6_K: 3.0 GB, comfortable fit; Q8_0: 3.4 GB, comfortable fit. A lower-bit file can move a result from too large to tight, but quality and kernel support may differ.
What can I run if LFM3-1.7B does not fit on AMD Ryzen AI Max+ 395 (Strix Halo) mini PC · 128 GB?
This selection already clears the comfort threshold. If you later increase the context, monitor the ceiling of 262,144 tokens; smaller alternatives include Flint 40B, NVIDIA Nemotron 3.5 Bolt E4B, Bonsai 2.
Is the speed estimate for LFM3-1.7B on AMD Ryzen AI Max+ 395 (Strix Halo) mini PC · 128 GB measured?
No. Very fast relative band is a heuristic band derived from 1.73B active parameters and 256 GB/s published memory bandwidth. Backend kernels, batch size, thermals, and CPU offload can change actual tokens per second.