Local AI Advisor

Can Surface Laptop Ultra · RTX Spark N1X (20-core) · 128 GB run Llama 4 Scout (109B-A17B)?

128 GB unified · 300 GB/s memory bandwidth · Llama 4 Scout (109B-A17B) has 108.6B parameters (17B active per token).

Short answer

Yes, comfortable for chat; borderline for agentic coding.

Best quantization for chat: Q4_K_M (61 GB of weights) on Ollama. Generation: 10–17 tok/s, leaving about 53 GB free for your other apps.

How it rates for each workload

Same model and machine, different jobs. Agents and long documents send far bigger prompts than chat, so they need much more speed and memory.

WorkloadVerdictQuantGenerationFirst replyContext
Chatwith Open WebUIComfortableQ4_K_M10–17 tok/sunder 1 s8KDetails
Coding questionswith ContinueAcceptableQ5_K_M8–14 tok/s≈4 s16KDetails
Coding in a repositorywith AiderAcceptableQ5_K_M7–12 tok/s≈10 s32KDetails
Agentic codingwith OpenCodeBorderlineQ6_K6–10 tok/s≈15 s32KDetails
Long documents (64K)with Open WebUIAcceptableQ4_K_M5–9 tok/s≈60 s64KDetails

Speeds are bandwidth-based estimates; no direct benchmark exists for this pair. “First reply” is the time to read the workload’s opening prompt. How we calculate

Get it running

Copy-paste commands for the Q4_K_M build with a 64K context. Ollama and llama.cpp download the file straight from Hugging Face.

ollama run hf.co/unsloth/Llama-4-Scout-17B-16E-Instruct-GGUF:Q4_K_M

This build is split into 2 files, which Ollama can't import from Hugging Face. Use llama.cpp or LM Studio instead.

Different tool, context size or workload?

These pages use typical settings. The full check models your exact setup.

Open weights (restricted)Check my exact setup