JournalINSTAGRAM

FIELD NOTE / INSTAGRAM

Kimi K3 is not a Mac mini workload.

The short film, the complete written thought, and the evidence behind it.

Published September 25, 2026 · Instagram edition

Kimi K3 is not a Mac mini workload.

Short video caption

Kimi K3 has 2.8T weights. At an ideal four bits each, raw weights are about 1.4 TB before overhead; Apple's current Mac mini tops out at 64 GB. Kimi recommends a 64+ accelerator supernode. Sparse activation cuts compute, not the memory/fabric problem. A local compact model can still be the right tool: compare first-token delay, throughput, concurrency, cost and accepted-task quality for your actual workload. Vendor specifications and lower-bound arithmetic, not a measured speed benchmark. #EricFieldNotes

Full written post / accessible read

Open weights give you control. They do not give a Mac mini a supercomputer's memory and fabric. Kimi describes K3 as two point eight trillion parameters. At an ideal four bits each, the weights alone are about one point four terabytes. Apple's current Mac mini tops out at sixty-four gigabytes.

A sparse mixture of experts activates only part of the model per token, which helps compute. The expert weights still need to be stored and fetched fast enough. Offloading to a drive may make something load, but it does not establish useful first-token latency, tokens per second or concurrent-user quality.

Kimi recommends a sixty-four-plus accelerator supernode for efficient K3 serving. For scale, one NVIDIA H200 has one hundred forty-one gigabytes of high-bandwidth memory. That is a hardware comparison, not a benchmark proving any particular throughput. An H200 cloud and a home box solve different constraints.

Use a compact local model when its measured quality and latency fit a bounded private task. Use a hosted or clustered frontier-scale model when the full model and concurrency matter. Record first-token delay, sustained tokens per second, cost and accepted-task quality. Do this because ownership of weights is not equivalent to useful service capacity.

#EricFieldNotes

Evidence and boundary

On-screen boundary: VENDOR SPECS · IDEALIZED WEIGHT MATH. The sources below support documented mechanisms and specifications; illustrative scenarios are not presented as measured incidents.

More notes from the work ↗