Control
The one machine running the scheduler, this UI, Postgres and control-placed runs: its CPU, memory, disk and network. The EC2 instances orca launches for runs are on Fleet; Watchdog lists the rules that pause pipelines.
Watchdog paused pipelines: control control instance memory 99.6% (limit 90%) (10h ago, 2026-11-07 02:09:41 UTC). Paused: gharchive_index, mojo_activity, mojo_history, mojo_repos, mojo_stats, mojo_versions. See why
Unpause a pipeline to clear its trip; Watchdog snoozes a rule.
CPU43%peak 57% in the last minute
Memory18%1.8 GB of 8.1 GB
Disk11%8.7 GB of 80 GB, under /var/lib/orca/stage
Network27.80 MB/sin; out 35.26 MB/s
Containers
| Container | Memory now | Peak in range |
|---|---|---|
| scheduler | 1.1 GB | 7.7 GB |
| postgres | 125 MB | 188 MB |
| console | 110 MB | 111 MB |
| cloudflared | 37 MB | 39 MB |
| ui | 20 MB | 21 MB |
| sampler | 11 MB | 11 MB |
Range: 24h 7d 14d (UTC, every 30 minutes; a point with no samples is 0)
CPU
Percent of all cores, user and system.
average peak %
Memory
Percent of memory in use (not counting the page cache).
average peak %
Disk
Percent used of the file system under /var/lib/orca, which holds Postgres' data and the staged logs.
fullest disk %
Network
Throughput over all interfaces but loopback.
in (MB/s) out (MB/s) MB/s
Container memory
Each container’s highest memory in the point, as docker stats counts it.
cloudflared console postgres sampler scheduler ui MB