Local AI Advisor

Can Surface Laptop Ultra · RTX Spark N1X (18-core) · 24 GB run GLM-4.7-Flash (30B-A3B)?

24 GB unified · 300 GB/s memory bandwidth · GLM-4.7-Flash (30B-A3B) has 31.2B parameters (3B active per token).

Short answer

It loads, but it's borderline even for chat.

Best quantization for chat: Q3_K_M (14 GB of weights) on Ollama. Generation: 70–120 tok/s, leaving about 0.0 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 WebUIBorderlineQ3_K_M70–120 tok/sunder 1 s8KDetails
Coding questionswith ContinueDoes Not Fit————Details
Coding in a repositorywith AiderDoes Not Fit————Details
Agentic codingwith OpenCodeDoes Not Fit————Details
Long documents (64K)with Open WebUIDoes Not Fit————Details

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 Q3_K_M build with a 8K context. Ollama and llama.cpp download the file straight from Hugging Face.

ollama run hf.co/unsloth/GLM-4.7-Flash-GGUF:Q3_K_M

Downloads 14.61 GB (Q3_K_M). Ollama's default context is small: set OLLAMA_CONTEXT_LENGTH=8192 before `ollama serve` for long prompts.

Different tool, context size or workload?

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