Skip to content

Host resources

Each connected host reports how much of its CPU, memory and disk is in use. You can see at a glance whether a VM has room for one more agent, or whether a full disk is about to stop a build.

On the Hosts screen, a strip under each connected host shows three meters:

  • cpu: a sparkline of the last two minutes, the current percentage, and the core count with the one-minute load average, for example 8 cores · load 2.41.
  • mem: a sparkline, the percentage, and the amount used of the total, for example 11.2 GB of 32 GB. When the host uses swap, the amount shows too.
  • disk: the percentage used and the free space, for example 48 GB free on /.

In a session’s status bar, at the bottom of the terminal next to the host name, a short reading shows the same three numbers: cpu 34% mem 61% disk 72%. Hover over a number for the details: the core count, the memory used of the total, or the free space and which disk it is.

A number turns amber at 75% and red at 90%. Below 75% it stays gray.

  • cpu is the share of all cores that was busy since the previous reading. Time a core spends waiting for the disk counts as idle, as it does in top.
  • mem is memory the system cannot hand out. File cache counts as free, so the number is usually lower than a simple “used” figure.
  • disk is the fuller of two disks: the root disk, and the home directory when it is on a disk of its own. The fuller one is the one that stops your work first. Space reserved for the root user does not count as free.

On a macOS host, memory reads higher than the memory pressure in Activity Monitor, because macOS reports only the memory that is free right now.

mocante shows readings for a whole machine only. It does not break them down by process or by session.

  • The host is not connected. Meters show only for a host in the connected state. See remote hosts.
  • The host has no mocante-agent, because mocante does not have one for its platform. mocante does not poll such a host over plain ssh, because each reading would start a new process there.
  • The first reading has not arrived yet. The sparkline starts after two readings.

Nothing while no view shows the readings. While the Hosts screen or a status bar with readings is open, your device asks each host for one small reading about every five seconds, over the connection it already has. Sampling stops about 20 seconds after you close the last view that shows readings.

Readings stay in the window for two minutes. They are not saved to disk and do not sync between devices.