Computers, terminal and Git

Check a Project's load history

See how hard a managed Project worked over time instead of guessing from one moment.

Open the history

Open Projects and select the managed Project.
In the Resources section, select the CPU, RAM, Disk or IO meter.

The Load history window opens for that Project. The same meters appear on a running desktop preview.

Open the period selector, which shows Last 24 hours at first, and pick Last hour, Last 6 hours, Last 7 days, Last 30 days or a custom range.
Tick at least one metric under Resources; more than one draws several lines.
Read the period shown above the chart. If it differs from your choice, Chetty adjusted it to the history it has.

History is kept for 30 days; the last 48 hours are detailed and older readings appear as hourly summaries.

CPU and memory show their share of the environment's limit in percent.
Disk shows its share of the Project's disk limit.
IO shows its share of the disk speed limit, or MB/s when no limit is set.
Network shows Mb/s.
Gaps are periods without a reading, not zero load. They follow a stopped environment or a missing measurement.
Brief spikes can fall between readings, and disk figures can lag by several minutes.
Last known figures marks values that are no longer live.

Tip: Open the history after a slow build or a failed command to see whether the environment was short of CPU, memory, disk space or disk speed.

Read Manage a managed environment to raise a limit or free disk space, and Projects overview for the other Project tasks.