How do you check memory usage (`free`)?

Fernando

Executing specific terminal diagnostics allows you to quickly evaluate systemic resource allocation and verify total hardware limitations. Furthermore, the standard free command provides a real-time snapshot of system memory, showing total, used, free, shared, buffer, and cache metrics. Why does appending the -h flag remain an essential step for translating raw bytes into easily readable formats like megabytes and gigabytes?

Beatrice

The `free` Command: Demystifying Linux Memory Metrics

Diagnosing resource constraints on a Linux instance is generally straightforward once command parameters are understood, but site reliability engineers evaluate several kernel utilization indicators before declaring a true out-of-memory emergency. The free utility provides a quick snapshot of physical RAM and swap space, extracting real-time metrics directly from the kernel virtual file system to expose exactly how memory allocations sit distributed across the runtime environment.

Core Command Syntax and Practical Execution

$ free -h
              total        used        free      shared  buff/cache   available
Mem:          7.7Gi       2.1Gi       1.4Gi       120Mi       4.2Gi       5.2Gi
Swap:         2.0Gi        0.0B       2.0Gi

Human-Readable Presentation (free -h): Executing the utility with the -h switch instructs the system to automatically scale metrics into easily digestible binary units such as Megabytes (Mi) or Gigabytes (Gi). Without this flag, the system prints long string values in raw kilobytes, which drastically slows down visual inspection during an active high-severity infrastructure outage.
Exact Metric Parsing (free -m): When automating monitoring loops via custom background scripts or parsing telemetry logs with processing engines, engineers run the utility with the -m parameter to output flat integers in Megabytes. This precise structural format allows mathematical parsers to evaluate system health trends cleanly without dealing with text suffixes.
Real-Time Continuous Monitoring (free -s): Observing volatile memory leaks requires tracking allocation fluctuations continuously over an extended window. Appending the flag followed by an integer—such as free -h -s 5—forces the terminal terminal view to dynamically refresh the usage table at that exact second interval until an operator sends an interruption signal.

Decoding Kernel Allocation Columns

The Used Memory Dimension: This value represents the exact amount of physical RAM actively locked down by running application processes and internal kernel structures. It explicitly calculates this metric by subtracting completely unallocated spaces, buffer segments, and system cache spaces from the absolute total memory available.
The Buffers and Cache Buffer Layer: Linux purposefully utilizes idle RAM to cache file system blocks and disk operations, ensuring high execution performance. Because the kernel can instantly reclaim and clear out this specific sector the exact moment an enterprise database or web service demands extra capacity, high cache numbers denote healthy, optimized kernel design.
The Available Capacity Indicator: Unlike the completely unallocated space column, this value estimates the true amount of memory ready to back new application launches without triggering disk paging. If this metric dips dangerously close to zero, the system stands on the verge of thrashing, threatening to deploy the out-of-memory killer daemon to terminate core tasks.

Balancing Active RAM and Disk Paging Governance

Engineering teams must constantly analyze the relationship between active RAM usage and swap volume consumption. When physical memory fills up entirely, the operating system shifts inactive execution pages onto slower block storage volumes to protect system stability. While minor swap footprint usage remains completely normal, rapid page spikes accompanied by high disk input/output wait times signal immediate memory exhaustion.