Documentation

GPUPeek

How to use GPUPeek to see GPU load and GPU memory, which processes use the GPU, and Neural Engine, GPU and CPU power on Apple silicon Macs.

Updated

The question it answers: how busy are my GPU and Neural Engine, and who is using them?

What you see

  • GPU busy, as the GPU driver reports it, with a chart since you opened GPUPeek. Apple GPUs also report renderer and tiler use, and the number of GPU cores.
  • GPU memory in use and set aside. On Apple silicon this is part of your Mac’s shared memory, and GPUPeek says so. Macs with a separate GPU show VRAM where the driver reports it.
  • Processes using the GPU, with each one’s share of GPU time since the last reading.
  • On Apple silicon, Neural Engine, GPU and CPU power in watts.

The Neural Engine

macOS reports no Neural Engine utilization to apps. The powermetrics tool shows it, but only to administrators, and MacPeek never asks for administrator rights. GPUPeek shows the power the Neural Engine draws instead, from the same energy counters powermetrics reads: 0 W means it is idle, and the number rises while an app uses it (dictation, photo analysis, Core ML and MLX models).

How to use it

  1. Open GPUPeek. It samples every refresh interval while its screen is open.
  2. Watch the busy percentage and the process list while the app you are curious about runs.
  3. On Apple silicon, check the Neural Engine power to see whether a feature really runs there.

Good to know

  • The power counters come from IOReport, an interface macOS does not document. GPUPeek loads it only if it is there; if not, it says power is unavailable and everything else keeps working.
  • Per-process GPU share and power need two readings, so they appear a moment after you open GPUPeek.
  • It only reads. Nothing is written and no permission is asked for.