Status
Start with Status for CPU, memory, battery, storage, and alerts. Availability depends on the Mac and the readings it exposes.
System
Use System for per-core CPU activity, uptime, load, memory, swap, network, storage, and user information.
Statistics and history
Statistics shows activity over time. MARC stores history on the connected Mac under the SSH account:
~/.local/share/marc/history.sqliteRemoving a Mac profile from iPhone does not delete this remote history or the Mac’s files.
Missing or stale readings
Check that the connection is active and Python 3 is available to the SSH account. Keep the Mac awake. A missing reading can reflect a permissions or collection problem rather than zero usage.
Reading the numbers
- CPU: how busy the processor is. A short spike during an app launch or build is normal; sustained activity is more useful to investigate.
- Memory: RAM used by apps and the system. A high number alone does not identify a problem—look at what is running and whether the Mac feels slow.
- Swap: disk space macOS uses to support memory. It is different from physical RAM.
- Storage: space used and available on a drive.
- Network: activity moving through the Mac’s network connection.
- Uptime: how long the Mac has been running since its last boot.
When something looks unusual
Look for a pattern rather than reacting to one reading. If CPU or memory stays high, open Processes and sort by that resource to see which apps are active.
Check storage separately if the drive is nearly full. Closing an app may reduce its memory use, but it does not remove files from the drive.
What history tells you
History helps you compare activity over time, but it is not a promise that every moment was recorded. Connection interruptions and collection problems can leave gaps.
The history belongs to the SSH account on that Mac. Connecting to another Mac or another account can show a different history.