Start with processes, networks, and ports when a Mac slows down
When a build, call, or local AI job slows down, one CPU percentage is rarely enough. Memory pressure, network activity, listening ports, and startup items can all add useful clues.
Follow the evidence one layer at a time
Better Monitor keeps the investigation local and structured:
- Start with the overview for CPU, memory, disk, network, and thermal state.
- Open Processes, Network Activity, or Ports to confirm resource details, connections, and binding addresses.
- When you need context, select one process snapshot for an optional AI summary, then decide what to do yourself.
Monitoring history stays on the Mac. AI is an explanation aid; it does not end processes, change startup items, or repair the system for you.
An observation is not a security conclusion
A local binding is not proof of public reachability, and a port hint is not a full security audit. Which processes, ports, and sensors appear still depends on macOS permissions and the hardware.