My Computer Is Slow or Running Out of Space

Use Metrics to identify whether slow work is caused by CPU, memory, or disk pressure. Check that the data is live before acting on it.

Find the pressure

1. Open Metrics on the affected computer.
2. Compare the current reading with the recent history.
3. Check CPU, memory, swap, and disk usage.
4. Scroll to Workloads and sort by CPU or RSS.
5. Identify the task before deciding to stop or change it.

A build may briefly use substantial resources. Persistent high memory usage or a nearly full disk deserves closer attention.

Inspect disk space safely

In the agent terminal, these commands report usage without deleting files:

df -h
du -h --max-depth=1 ~/projects

Use the second command only for a folder that exists, or replace it with your project location. It can take time on a large directory.

Common growth comes from dependencies, build outputs, caches, logs, and local datasets. Delete only data you understand and can recreate or have backed up.

Reduce competing work

Stop an unnecessary development server or pause another heavy task through its normal controls. Reduce test parallelism where the project supports it and use Guard for heavy suites.

If the regular workload still exceeds the plan’s capacity, consider an eligible upgrade after saving work. More RAM does not fix a provider rate limit or a network outage.

See resource monitoring, Guard, and plan upgrades.