Who it is forA developer on a PC with an NVIDIA or AMD card who runs Ollama and suspects a model is spilling onto the CPU.
The problemWhen part of a model sits on the CPU, generation becomes much slower, and Ollama does not make that placement obvious at a glance.
The outcomeThe Overview verdict names a model partly on the CPU, and the loaded model list shows its VRAM and CPU or GPU placement.
What you need first
- macOS 11 or later on Apple Silicon, Linux (x86_64 or ARM64), or Windows (x86_64)
- A local LLM runtime such as oMLX, Ollama, llama.cpp or vLLM installed and able to serve a model
- A terminal, or Rust 1.88 or newer if you build from source
Steps
- Install Mlxtop with the install script for Linux, or
brew install maximpri/tap/mlxtopon macOS or Linux. - Start Ollama and load a model by sending it a prompt.
- Run
mlxtopand open view 1 · Overview. - Read the loaded models and their CPU/GPU placement, and check the verdict line for a model partly on the CPU.
- Use
[and]to select a GPU card if the machine has more than one.
Prompt for your agent
Using the mlxtop repo at maximpri/mlxtop, start a loaded Ollama model on <target machine>, run `mlxtop --once`, and report the loaded model name, its VRAM use and its CPU/GPU placement. Verify the report shows the placement before you say whether the model is partly on the CPU.
Caveat. For Ollama, speed is recorded after each request completes, so live tokens per second are not shown while a reply is still streaming.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for maximpri/mlxtop and "Spot an Ollama model partly running on the CPU"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer