Fit uses a source-backed memory profile; direct speed coverage is still missing MiniMax-M2.7-3bit source profile lists 112 GB minimum memory on MLX; throughput still needs direct benchmark coverage.
Direct trusted-reference benchmark coverage on this hardware class Speed is backed by trusted-reference benchmark coverage. Most common runtime in the evidence is Ollama.
Direct trusted-reference benchmark coverage on this hardware class Speed is backed by trusted-reference benchmark coverage. Most common runtime in the evidence is Ollama.
Direct trusted-reference benchmark coverage on this hardware class Speed is backed by trusted-reference benchmark coverage. Most common runtime in the evidence is Ollama.
Direct trusted-reference benchmark coverage on this hardware class Speed is backed by trusted-reference benchmark coverage. Most common runtime in the evidence is Ollama.
Direct trusted-reference benchmark coverage on this hardware class Speed is backed by trusted-reference benchmark coverage. Most common runtime in the evidence is MLX.
Estimated from nearby benchmark coverage, not a direct match Speed is estimated from nearby benchmark coverage rather than this exact machine-and-quant match. Best runtime hint: Ollama.
Coverage
No direct benchmark rows yet
Speed is estimated, so this cost read is provisional.
Direct community benchmark coverage on this hardware class Speed is backed by community benchmark coverage. Most common runtime in the evidence is MLX.
These answers stay tied to the live workspace defaults for this compatibility route, so the copy explains the same sort order and query framing the table is using.
What does the Run route optimize for?
Run starts with a Mac and sorts toward the most capable models that remain practical on that machine. It is the fastest way to answer what your current Mac can run locally without guessing from raw memory numbers alone.
Why does Run show models instead of Macs?
Run flips the workspace into Mac-to-models mode. Instead of asking which Mac to buy for a model, it asks which models remain usable on the Mac you already own or plan to deploy.
How should I interpret the evidence labels on Run?
Benchmark-backed rows have direct speed evidence, with Lab, trusted-reference, and community labels showing provenance. Estimated rows are derived from adjacent evidence, and fit-first rows are memory-feasibility reads.