STACKMODERNE
Efficiency and substrate affinity / GUIDE

Run an LLM on CPU: method and limits

Evaluate CPU LLM inference with quantization, memory, context, throughput, concurrency and explicit capability gates.

ENGINEERING THESIS

CPU inference becomes relevant when capability is bounded, the model fits and workload matches the hardware.

COMMON FAILURE

Saying a model runs on CPU proves neither user latency, concurrency nor capability preservation.

DECISION

The verdict must bind the exact CPU, thread count, GGUF, runtime and workload profile.

01 / REALIZATION

What the architecture must make explicit

Cost is reduced at realization level: avoiding calls, shortening context, quantizing, routing or rematerializing a responsibility can matter more than isolated model optimization.

01
Model and quantization
02
Context, cache and retrieval
03
Routing and activation
04
Rematerialized deterministic functions
02 / METHOD

Move from a keyword to an inspectable engineering decision

01

Profile

Measure actual system costs, including retries, transfers, memory and verification.

02

Attribute

Determine which responsibilities still require a powerful model.

03

Transform

Test reduction, quantization, specialization, caching, routing or substitution.

04

Compare

Keep the same capability contract and publish exact hardware conditions.

03 / EVIDENCE GATES

A claim is only as strong as its binding

The gate must evaluate the exact output produced by the exact realization. Integrity, scientific validity and authority are related, but never interchangeable.

G1
Capability preserved
G2
p50/p95/p99 latency
G3
Memory and concurrency
G4
Cost per admissible result
FAQ

Questions that change the design

What does run an llm on cpu: method and limits require?

CPU inference becomes relevant when capability is bounded, the model fits and workload matches the hardware. Cost is reduced at realization level: avoiding calls, shortening context, quantizing, routing or rematerializing a responsibility can matter more than isolated model optimization.

Which evidence should be retained?

At minimum: exact realization identity, inputs and outputs, protocol version, measurements, failure cases and the decision rule. The verdict must bind the exact CPU, thread count, GGUF, runtime and workload profile.

Does AMF prescribe a particular model?

No. AMF treats the model, runtime, data, tools and deterministic components as candidate materials. Their retention depends on measured contribution and declared constraints.