Hardware

MEGATRON is a workstation-class server built for parallel compute workloads -- deep learning training, Kubernetes orchestration, and multi-tenant application hosting.

CPU

Memory

Note: 21 GiB of swap in use despite 206 GiB available RAM suggests processes were swapped out over the 37-day uptime and not yet paged back in. Consider a targeted swapoff -a && swapon -a cycle during a maintenance window if swap pressure becomes a concern.

GPUs

See GPUs for detailed GPU information including driver version and active processes.

System Load

With 128 logical threads, a load average of ~20 represents approximately 16% CPU utilization. The steady load across all three windows indicates consistent background workload, likely from K3s cluster operations and running pods.

Resource Usage Summary

CPU:  [####................] ~16% (load 20 / 128 threads)
RAM:  [###.................] ~17% (42 / 251 GiB)
SWAP: [##############......] ~68% (21 / 31 GiB)
GPU0: [##..................] ~11% VRAM (2.7 / 24 GB)
GPU1: [....................] ~0%  VRAM (14 MB / 24 GB)
ROOT: [###########.........] 54% (1.6T / 3.1T)
SMB:  [##################..] 90% (79T / 88T)

Top Processes by Resource Usage

At the time of audit, the primary consumers are:

• K3s server and agent processes -- Kubernetes control plane and kubelet
• containerd -- Container runtime for all K3s pods
• cloudflared -- Cloudflare tunnel daemon
• AlertManager -- At 203% CPU (known issue, see Current Issues)
• VNC server -- In restart loop consuming resources (known issue)

Peripheral Notes

• Storage: NVMe primary (3.1T), SMB network share (88T), NFS mounts (currently down)
• Network: Dual-stack networking with Cloudflare tunnel, Tailscale mesh, and direct SSH
• The system runs in a DEGRADED systemd state due to failed motd-news and wol-enable services (non-critical)